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.
  • It takes a LOT more than that to embarass me.
  • "Perl 6 is to Perl 5 as C++ is to C"

    Ergh. One of my goals for the design of Perl 6 (and Parrot) has been to encourage us not to make the mistakes of C++. (Sometimes I flatter myself by thinking that roles are a better basis for a type system than the number of bits you can flip before crashing.)

    • That wasn't what I meant. I wasn't trying to make any comparisions between the design, but the way that C++ took C into a different sphere of programming, and the fact that C itself is still around.

      Perl 6 is likely to carve a new path for itself, but Perl 5, like C, is not likely to disappear any time soon.

      • That makes sense. Still, I do worry that people will think "Wow, C++ is a dog's breakfast of a language compared to C. Perl 6 must be a mess."

  • It would appear that Twitter is using Ruby.

    Dunno if we count that as "big-name" but it certainly lets me keep my slogan

    "Ruby - It's where the hype is!"
    • I can't help but wonder what will happen to Ruby once the next cool and trendy thing happens.

      To be honest what I've seen of Twitter doesn't make me think it'll be top of the cool and trendy list for very long. The SMS side of things will soon lose it's flavour once the spammers realise how useful it is.

  • Part of the problem is that perl is still ubiquitous but only the old hackers know it.

    As you've probably noticed, the ignorant tend to fear what they don't know in order to rationalize their ignorance. So they hate on perl, partly because they haven't bothered to understand it, and mostly because they're scared as hell of the bears around the office who seem to know it really well.

    It's ugly, it's antiquated, it's whatever. Just as long as I have some legitimate reason for hating on it, so I can justify why
  • 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 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.