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.
  • I've been moving towards Ruby too. I hear there is strength in numbers. Andy Wardly likes Ruby as well. Hey, garbage collection is nice you know :)

    • Hey, I like Ruby too. :)

      It may well do to perl's user base what Python never did. (Or could, I think)
  • This is pretty much all we need :-) I'd switch right away... It might require porting some stuff from CPAN, and running a little SOAP server to access Perl for a while, but so many things are just done right there that it's very tempting.


    -- Robin Berjon []

    • Be warned, the previous comment comes from the same guy (or gal?) who tempts people publicly (or at least in IRC) to make a switch to Postgres (from MySQL). Everytime I see that guy on PM with red eyes, I think of darobin! ;)


      • I'd venture to make the same suggestion. The slowdown with Pg is probably about 10% now from MySQL, which is negligable, but Pg will also be much faster on complex queries, because frankly it's query optimiser is light years ahead of MySQL's. In fact I'd say it's as good as Oracles (though maybe not as good as Sybase's).
        • arg - not you, too! *laugh* Seriously, I do envy having foreign keys, stored procs, views and triggers, but not at the current expense of rewriting a massive amount of CGI programs.

          Hmm ... maybe I'll write my new stuff using Pg (I do have a server running in conjunction with MySQL)... that'll be my entry into the dark side.

  • Oh yes, it's lovely isn't it. I've kind of fought shy of doing anything serious in it, but I'd *love* to see large chunks of the Ruby Way making it into Perl 6.