This is a very good idea.

The issue with the reviews is that there are not enough of them. With many (most?) modules it isn't just a matter of "not enough to determine quality" - there aren't any!

CPAN won't see a great volume of reviews without serious thinking and work going into the review system. Which is why I like your idea: it is simple, and gets the job done. If even a few reviews that said "This module is a 4/5, it does X well but if you want to do Y too you should look at module Z" it would help me track down my best-fit module faster.

I think I'll start adding reviews like this when I find a set of good, related solutions.

In reply to Re^3: Using CPAN effectively; Finding the best fit module. by amarquis
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.