Re^2: How does one choose among modules?

As for actively maintained modules, you're right. If all the bugs are out and the module has the complete feature set intended by the authors, there's no reason to rate the module down for not being updated recently.

The rest of your points I'll not mention specifically because I have no disagreement nor comments to expand on your reasoning.

What would you think of a web page with a table listing ratings for all of these things for all of, say, the PDF tool sets? I'm not sure that's the ultimate solution that I'm looking for, but it's one of the ideas that comes to mind. Of course, one might want empirical measures present separately from subjective ones or given more weight, but those are implementation details.

Comment on Re^2: How does one choose among modules?

Replies are listed 'Best First'.
Re^3: How does one choose among modules? by frostman (Beadle) on Oct 11, 2007 at 02:33 UTC
For things that are (nearly) objective I think it would be cool to have such a chart, and not just for "competing" modules. Say, everything to do with PDF: CPANTS pass/fail rate Most recent version Rate of new version releases Pod::Coverage result (or similar) Perl::Critic result (violation by severity? ...and so on... All nicely sortable or course. But excluding anything you can't back up objectively, so no "five stars from me" type of stuff. In fact it might be really cool to do that for all of CPAN and let you sort/filter/etc on it.... but I'm not volunteering, too busy myself these days.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.