It's all Darwin, survival of the fittest. Over time, the best modules are most likely to survive. Programmers will communicate and mention those modules they find most useful. When others need a module to do a specific task they are most likely to choose those they remember having heard the most positive things about. Evolution in action.

I have used the word most more than once(by design, really!). Programmers are people and people can be fickle and illogical at times. Sometimes a module will be popular though there may be better modules doing the same work. A situation somewhat like Betamax versus VHS. A rating system does little good in such cases because ratings in the final analysis are a measure of popularity. Does such popularity make a module fit? No, but it does make it a survivor.

The point I am laborously trying to make is that pollution can be hard to get rid of. I believe the best solution is to let the module users select the modules that are best. Not a perfect system but none is and better than selection by committee (or, god help us, management).

xenchu

The Needs of the World and my Talents run parallel to infinity.

In reply to Re: What do we mean with "CPAN pollution"? by xenchu
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.