NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Tell Me About It...? (Score:2)
This week I'm on a SAP training course learning their XI/PI middleware application. It's built on a mixture of their legacy ABAP (COBOL like) technology and all new Java code. Internally the whole middleware engine uses a proprietary form of SOAP to send messages along their system. It's little more than XSLT with bells on but it's horribly slow and bloated.
In the class, a colleague mistyped a parameter instead of raising a sensible error message, Java dumped and he got a Java stack dump thing. I don't like the idea that a standard SAP provided JAR just falls to pieces if you send something in it didn't expect.
One thing I found interesting on the course so far has been that the other technical people all have a low opinion of Java - it's not just me. The instructor likes Java but he isn't a programmer... The more functional types seem to be more positive about Java, strange as they don't use it or see it.
Even ignoring SAP's Java bloat, they do their own XML which isn't real XML - though I've not been able to pin them down on exactly what part of the XML standard they don't support.
-- "It's not magic, it's work..."
Reply to This