Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Oh, yes, we're on use.perl.org, 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 able to hire a Perl programmer? will you be able to find out-of-the-box solutions that you can buy rather than spend more money on developers?

    Writing a JAPH or obfuscated quine is great when you're at the university, and the Perl community > *, but pretty much anything "enterprise" sucks in Perl. No? I think that's why people think Perl is dead. If I were starting out programming, I certainly wouldn't go with Perl.

    • 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 [elharo.com]. 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 hea

      • 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*
    • .... but pretty much anything "enterprise" sucks in Perl.

      I've seen my fair share of "enterprise" software written in plenty of languages. I'm not sure that the suckiness is Perl's fault. There was certainly more than enough to go around.