I think that one of the problems with CPAN is that new modules have a big disadvantage in respect to older ones.

Older modules have the best namespaces and are referenced in forums, magazines, books, etc. so people searching for something will find them first. Even PerlMonks is very conservative in that regard, because people recommends what it knows and use and for the same reasons, they tend to know old modules better.

That happens with File::Find, google for perl find and the first entries point to it, both "Learning Perl" and "The Perl Cookbook" talk about it, it's even on the core!

In reply to Re: Using CPAN effectively; Finding the best fit module. by salva
in thread Using CPAN effectively; Finding the best fit module. by amarquis

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.