Given that every user has a personal favourite which might not apply to other users it seems logical that over time "all" modules would have to be included in the list.

Because for any given module $foo there is almost certainly a user or two who believe that is the world's best module!

For that reason above all I think that such a list wouldn't be as useful as you'd imagine:

What I would suggest is twofold:

1. Add a rating to the module review section and use that in preference to a new section.

2. When you say you don't have time to keep up with CPAN that is reasonable (and common!) but I think it is almost mandatory to have a quick look when working with a new area.

Taking you as an example you say you do mostly "databasey" things. I'd not expect you to look at every type of module available every day, but I would imagine that you would have a quick look if you wished to start workgin with say CVS code.

Does that make sense? Having the "best module" cover some modules for working with CVS servers might stick in your mind, but I'm sure that people who know of CPAN and are working on a new area would be liable to search there first, even if they weren't sure of what was available.

Steve
--

In reply to Re^3: Section proposal: Best CPAN Modules by skx
in thread Section proposal: Best CPAN Modules by ptum

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.