Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • And no one is impressed with your httpd/roman numeral calculator, turn to Sun for even more ridiculously verbose and convoluted solutions to problems you never had in the first place.
  • XML is a fantastic tool, but trying to beat all problems into submission with it is simply ridiculous. What on earth is Sun trying to solve with XPRESS (with they describe as a "scripting language") that requires the verbosity of XML?

  • The (false) laziest language designers and implementers in the world? "Grammar? Parser? Eh, just use XML." To paraphrase Matt Robinson [], whenever a programmer thinks 'I'll just use XML' their computer's speakers should create some sort of cock-shaped soundwave and plunge it repeatedly through their skulls.

    Patrick quoted Larry Wall in his Perl 6 talk to the effect that language designers torment language implementers to the benefit of the users. This would appear to be the opposite.

  • 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

    -- "It's not magic, it's work..."

  • block{
          s{Hello there!}
          add{ i{100} i{2} }

            substr{ ref{accounts\[Exchange\].firstname} i{0} i{1}}

    Yeah, still ridiculous, but co