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.
  • Oh, yes, we're on, so we're all going to be defensive and praise Perl, but let me point out that:

    * she used to work for Playboy, and it was Perl at both ends.

    Try to:

    • use Perl with WSDL - it sucks compared with VB or Java
    • use Perl to write a GUI - Perl blows
    • use Perl for practically anything on Windows - there are generally other tools which are more productive than Perl

    That's just a few examples related to the language itself, then there are other business considerations like: will you be

    • WSDL blows anyway, there is very little interoperability if you try complex data structures and don’t use the same language on both ends of the wire. The whole WS-(Death)* stack blows anyway []. Of course it’s no surprise to see good support for that pile of cow manure in MSFT and Sun products – both companies have bought heavily into the approach, and both follow the “tools will save us” mentality.

      Gtk2-Perl works just fine, though it’s not advisable on Windows. I also hear that the Cocoa bindings for Perl are very nice.

      Yes, Perl on Windows is a pain. Frankly, while I rationally understand that this should be a concern, I simply can’t find it in me to care much. Meh.

      The one thing that actually worries me about Perl is that the build toolchain stems from an era where Unix sysadmins did all the systems work, and is just about good enough to use but too hard for casual users (and non-programmers) to get to grips with.

      Besides this one point, I don’t see anything that Ruby or Python can do for the enterprise that Perl can’t.

      • wxPerl is pretty mature at this point.

        Perl on Windows hurts only because qdos hurts. Mingw is ok and Strawberry is about as good as Perl on qdos can be. But, mingw32 on Linux is probably *the* way to go. Just need to get rid of some $^O runtime assumptions in the toolchain.

        The toolchain is only a difficultly if we continue to assume backwards compatibility to about 1995. For those just joining us, it can be much easier (and possibly even GUI (see wxPerl.)) There is, of course, the problem that *nobody*