While vetting things to write up for the calendar I often come across multiple symmetric objects which can allow an object riding on an axle mounted to the item to glide forward at a constant height (a wheel). And I often think about a giant matrix of related modules comparing feature sets, bugs etc. As potentially useful as it might be it'd be no easy task I tell you what. Consider a matrix of template modules, and how many toes you'd step on. *shudder*

Of course I don't totally buy the "cream always floats to the top" argument either. If I did it'd be hard to work on the calendar. Somebody (or more likely many somebodys) has to "discover" the module in the first place.

I would like to see more considered/extensive evaluations, heck more evaluations period, on ratings, anno etc. However I think this will continue to be difficult for many reasons, not the least of which is the disjointedness of search, anno ratings, rt and cpanforum (completely and totally seperate for no apparent reason). It'd be great to have a single master cookie for everything but PAUSE (and for RT, only allowing new ticket/comment operations, not full editing abilities) in *.cpan.org...

UPDATE: I have it on good authority that the powers that be are in fact working on unifying the auth systems at this very moment.

--
In Bob We Trust, All Others Bring Data.

In reply to Re: Negative module recommendations by belg4mit
in thread Negative module recommendations by zby

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.