I guess it would have been nice if you'd have posted a bug report. I realise that sometimes time constraints don't allow for writing up a sensible bug report with all necessary information, but if you really like the module that would have been the way to go IMO.

That's also my reaction to your OP, there are two good ways of constructively criticising a module. If you think it's irredeemably broken or ill conceived you can say so on cpanratings and give detailed reasons. Otherwise, if you think the module is good in principle but is lacking a feature or has a bug you can file a bug report/wishlist on RT and help the author improve it. Your notion of helping users pick the right module is a good one (and the wish of a more reliable quality rating for CPAN modules is often expressed), but ultimately it's more worthwhile to worry about the code rather than the "marketing" (used here in the loosest possible sense).


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re^3: Negative module recommendations by tirwhan
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.