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.
  • The whole set of blogs connected to Andy Lester's TIMTOWDI interpretation [perlbuzz.com] is a valuable one.

    Brian Foy's crystallization [perl.org] of the difference in viewpoints as "Diversity is the New Uniformity" is apt.

    Perhaps we can say the dialectic is one between the new and the old. Old (established) beats new and new beats old. Can't live with it. Can't live without it.

    Zbigniew Lukasiak links to an eye-opening Puppet discussion of ruby gems [madstop.com] and other languages' distribution problems, contributed to by Russ Allber
    • I think Perl really benefited from appealing to the sysadmin crowd back when it did. The people who set up CPAN were sysadmins, not programmers, so they approached the question quite differently from the various people who’ve tried to create a CPAN clone for another language in more recent times. Most of them try to recreate everything provided by the entire CPAN infrastructure, and then add even more features, in one fell swoop. Even the CPAN6 project fell into this trap. In contrast, sysadmins tend to abhor complexity and distrust abstractions, so they built CPAN the only way it could work: in layers, each the simplest thing that could possibly work at that point in time. And thus Perl has CPAN and other languages do not.

      It’s a bit of a happy accident in some ways… though not an accident at all in other ways.