Having lots of modules that duplicate each other's functionality can be a problem in that new users have trouble finding the best ones and waste time, possibly also getting frustrated with CPAN and going sour on the whole idea of sharing code. Think about the torture awaiting a person who types "template" into the CPAN search engine.

Unfortunately, the metrics you talked about are not very comprehensive at this point. Maybe some day we will have enough votes for them to be more useful. Meanwhile, we have ad hoc attempts, like my article on templating systems. Several people have asked me to add other modules to this document, but in most cases I have to refuse, since the whole point of having this sort of document is to steer newbies toward the cream of the crop. Experienced people who have something specific in mind can handle examiing the suff on CPAN and deciding for themselves.

One thing that may help is the work that Leon Brocard did on CPANTS. He made some first steps toward automatic evaluation of modules based on some simple statistics. This could eventually be very helpful in fiding the best modules.

In reply to Re: What do we mean with "CPAN pollution"? by perrin
in thread What do we mean with "CPAN pollution"? by bronto

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.