While you may have a point your arguments do show why it is often difficult to have negative reps on modules. There are ratings, bug reports and documentation for a reason. After reading the docs and (where necessary) experimenting with the module you are in a position to decide whether it meets your needs.

For example, your initial point: 
#  Class::DBI::Pager - that module does not use 'LIMIT' clauses in the
+ database, there are better alternatives.

[download]
I use SQL server. Additionally, a brief (very brief) scan of the alternatives - well one doesn't support Oracle or DB2. So I have to write my own limit syntax/code anyway. As my workplace uses those three DBs exclusively. No postgres and no mysql. Period.

I'm not saying your criticism is not unfounded, but it doesn't help me as the syntax you complain about is not available to me regardless.

Would it not be better to offer solutions to problems?

Finally, you recommend an experimental module as part of your "review". Where I work, experimental code cannot go on a production system. Period.

Just my 2p so please take in the same vein :).

In reply to Re: Negative module recommendations by simon.proctor
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.