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.

How many CPAN modules on the same topic is too many? 2 Comments More | Login | Reply /

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

  • book of all the most frequently annoying questions and criticism of the CPAN and post it somewhere...not that it would ever get read, but at least I'd have cut and paste.

    Nobody ever asks why there are 15 different mustards to choose from in the grocery, so I'm never quite sure why people get fussy about the selection on CPAN unless a) they have a module that fits in a namespace they want but is already taken or b) think everyone elses' module is shite save for theirs. It's a free archive...pick and choo

    • If you had watched the video, you'd have perhaps gotten my point.

      If you offer people 24 mustards to try from, lots of people will come and look, but not many will buy.

      If you offer people 6 mustards to try from, fewer people will come and look, but MORE people will buy.

      That is the critical point here.

      Where I'm curious about is IF this applies to CPAN modules.

      I'm not complaining that it does.

      I don't know anyone left related to CPAN, me included, that honestly thinks that only having one choice for a single topic is a good thing.

      The trainers understand this as well. They aren't idiots.

      But that doesn't avoid the problems they have with students, especially ones for who programming Perl isn't what they want to do with the rest of their lives, and they are just trying to get through the assignment.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.