comment on

You've got a good point - is sheer volume worth the loss of quality? However, Borisz also pointed out two issues - 1) who's going to be the judge, and 2) what happens to if things break when supposedly poor-quality stuff is removed.

Perhaps a way around this would be to have two sections on CPAN - one for general modules, and another for modules that have been "certified" or otherwise validated or recognized. I don't know how practical that would be, but at least it would reduce the likelihood of modules being removed that someone relies on.

I didn't understand your comment about having a better implementation, but not being willing to contribute it to thisCPAN. Why not? I can't see that it would do you any harm. But of course, that's your decision...

בּרוּך

In reply to Re: The quantity vs. quality lesson by baruch
in thread The quantity vs. quality lesson by PetaMem

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks