in reply to
Re^2: The quantity vs. quality lesson
in thread The quantity vs. quality lesson
"You don't find often books of 1st grade students in the university libraries"
Awesome point. Very concise. You should have led with it as it would make your argument for "levels of CPAN" more clear. Perhaps (though I have alluded to it), we should have varying levels of approval, such as in the Debian system, where private packages can be seperated from the "uber packages", making it easier to tell what you are downloading. That sort of direction is *definitely* an improvement and is doable, much easier than just begging for quality.
I am disappointed your requests for quality are falling on deaf ears and we're hearing "but I should be allowed to upload my buggy code and bad designs!". I think, once, CPAN served a place like that. But this is horrific on the users, and that time has gone. If we want to establish a CPAN experimental, unstable, testing, and stable, that's fine, and I will gladly set my configuration files to not search through it!
Anyhow, if Perl is to grow up, it needs to take on a better goal of quality, not quantity. Quantity is for first graders, and I want rock-solid code, because I write rock-solid code. Modules that are halfway-implemented source filters or broken implementations do not intest me, and we need a way to seperate the wheat from the chaff. Not to grade the wheat and the chaff, mind you, but to organize it.
Something also needs to be done about namespace sprawl to confine modules to more logical places.