I prefer to have 900 good modules in 10000 modules (9% of quality), that have only 90 module in 100 (90% of quality)
Who is to say this is the bar? This is a weak argument. The problem with CPAN is it lies in anarchy as compared to other languages "core", and often it is hackish or bug-ridden or incomplete, or documentation is woefully inaccurate or missing. And this is somehow ok. Well, yes, CPAN is a public happy place... but there is this phenomenon of the "tragedy of the commons", and CPAN is thus full of proverbial space junk. Can we fix it? Yes. Should we? Perhaps not... but we need to raise the bar and move to a more Debian-like system of maintainers -- and a system where orphaned packages can be adopted if the owner is gone. We should also work on solid frameworks to limit the "TIMTOWTDI" phenomenon. More than one way is fine, but I don't want incompatibile ways ... i.e. this module has an OO interface, this one doesn't, this one uses this module ... it just results in code looking sloppy. Perl is a very powerful language, but I wish the community had higher standards. I'm not embarassed for asking for it, and this isn't a knock at Perl.

In reply to Re^2: The quantity vs. quality lesson [my MANIFESTO] by flyingmoose
in thread The quantity vs. quality lesson by PetaMem

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.