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.

No C for me thank you 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • One of my personal theories for why Ruby, etc., are more successful recently is that they abstract away more than Perl does, or at least they abstract away more important things. It's not so much the languages themselves but the mindset of the communities. It's one reason why I don't think Perl 6 is going to "turn things around" for Perl. [skip list of disclaimers for warding off flames :} ] We're going to end up rewriting a lot of existing functionality in Perl 6, but I don't think that will lead to more a

    • One of my personal theories for why Ruby, etc., are more successful recently is that they abstract away more than Perl does, or at least they abstract away more important things.

      Declarative classes (seriously, @ISA in 2008?) and blocks (such as they are) really do help Ruby abstractions.

      We're going to end up rewriting a lot of existing functionality in Perl 6, but I don't think that will lead to more abstraction.

      Multidispatch, to choose one random feature, really improves abstraction and conciseness -- and the declarative syntax pushes the cost of the feature down. Roles may be a better example.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.