I don't disagree with your observations of the module being buggy. You posted your review of it both here and to CPAN's bug tracker, great.

It is possible to offer constructive helpful criticism without being so inflammatory. Instead of helping to facilitate progress, your comments will more likely cause separation and conflict.

Perhaps he wrote a buggy module. Perhaps it works great on his system in the circumstances in which he uses it.

Perhaps his code is not as efficient as you could write it, but the beauty of Perl has always been that there is more than one way to do it. If you want to help the advancement of Perl and CPAN, offer him constructive examples of how something may be written more efficiently.

Where the name is concerned: open source project have all kinds of screwy names. How about Perl, Apache, PHP Nuke, Jakarta, Tomcat and Ant. Heck, just look on freshmeat.net any given day for bizarre names.

It is up to the PAUSE moderators to approve or disapprove name spaces. When I first submitted the module registration DBIx::Loop, Tim Bunce kicked me right and left until we ended up with DBIx::FetchLoop.

In the comments here, you were quite full of righteousness over the level you've reached here. Pride is not constructive and it will not benefit you in the long run. I implore you to stop and think about the best possible solution for an issue and figure out how to reach it without causing conflict.

In reply to Re: Handy dandy CPAN pollution by suburbanantihero
in thread Handy dandy CPAN pollution by Juerd

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.