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.

The Real CPAN Limitation 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This, incidentally, is why I'm bullish on Perl 6. It appears to solve most of my Perl 5 problems. Tim Bunce has already mentioned that he plans to port DBI.pm to Perl 6, a Perl 6 CGI.pm won't be far behind (it might even be first) and I suspect that a few other core tools will quickly get ported. With those in place, and given that the real value in a business is the in-house code, if Perl 6 is stable and runs as fast as we suspect, maybe I won't be eyeing Ruby with such longing.

    What are you expecting to

    • I can certainly work with Ruby more, but only on a side basis. For day to day work, I'm still stuck with Perl. And still happy with Perl, to be fair. It's a great language.

    • What are you expecting to get out of Perl 6 that you won't get from Ruby, other than a speed advantage?

      An upgrade path. (Not that a speed advantage is a bad thing with the amount of traffic we have...)

      Seriously where I work we have about 3 years of Perl code accumulated. Suppose that Ruby is 30% more productive than Perl. Then (by a naive calculation) if we switched, it would be 10 years before we had caught up and passed where we are now. That's not even counting the mess of going through a period w
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.