|Problems? Is your data what you think it is?|
Update: I cleaned up my language. I was pretty angry when I first wrote this
CPAN's philosophy has always been to release early and release often. We want people to upload instead of hiding code in some silo until they think jerks like you will approve and bless it. We want people to put up their work as early as possible so other people can help them with it. Even with my years of experience, I still make some of those mistakes (like the stupid ._ files that show up every time Apple changes the special environment variable for their own tar).
So what if the module sucks now? People can see it and help the original author improve it. That's the point of open source. If the Perl community had your attitude when I started, I probably wouldn't be involved with Perl at all.
This is becoming more and more of a problem with the Perl community. Perl Best Practices gave jerks a new way to attack newbies for doing newbie things. I'm genuinely sad when I see a rabid gang of PBP police go after someone who's obviously new. In the big scheme of things, newbies need gentle introductions and guidance when they start, not nitpicking and pedantic attacks about Pod, whitespace, and so on. This sort of crap drives away any of the new blood that Perl could use. It's even driving away some experienced people as the new braindead megaphones crowd out the sensible developers.
If you really wanted to help, and I don't think you do, you'd pick a couple of important things to help the author with, or even make the patches to fix some of these trivial things. Instead, you simply want to gloat with all your Perlmonks buddies about how you're better than some newbie, all the while hiding beyond Anonymous.
brian d foy <firstname.lastname@example.org>
Subscribe to The Perl Review