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.
  • Don't filter CPAN. Only knock modules off if they have malicious intent.

    Instead, create bundles of the best modules. Phalanx has a bundle... anybody can post a bundle... don't filter out crap, point out the shining stars.

    A step further than that, I see a real business opportunity in creating a filtered mirror of CPAN modules. This mirror can contain modules that are useful, safe, and proven via tests and so fourth. Corporations will buy into a 'trusted' and 'supported' set of modules on CPAN. Thi
    • I'd be quite interested in a commercially supported core set on modules. I'm sure that could be very useful when you have smaller businesses with only 1 or 2 programmers and no time to evaluate, debug and test CPAN modules.

      The ratings site is quite useful, if underused. I'd like to see some kind of organised best-of-breed site that combines recomendations, with pointers to articles and feature comparisons...

      Yes I was on, yes I too muttered about bloody stupid modules, but also the number of times many of us have uploaded a module 2 or 3 times in a few minutes because everybody makes mistakes (and usually spots them a second after the module arrives in the PAUSE queue and is announced everywhere).

      Feeding off the idea mentioned on irc about people responsable for namespaces, it would be nice if you had somebody who put together a comparison/guide to particular areas handled by CPAN modules, with best of breed, articles, books, mailing lists, etc. That would really "add value" to CPAN.

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • Late in mentioning... but doesn't ActiveState fit the "commercially supported core set on modules". They certainly sell themselves that way (even if I only use them on WinTel).

        On the topic of stupid modules... User naiveity, more often than not, is the cause of crap. The whole "My situation is unique, so I'll code and upload my own quick and incomplete solution without looking to see if something else comes close," attitude.

        Luckily, by virtue of the amount of energy it takes, it's relatively rare. At l