comment on

This post is a sacrilege. :-)

CPAN at this time contain ~3000 modules. If you search CPAN for something and you don't know exact module name and just search by category and keywords - your chances to find the best of existing solutions are near ZERO! As merlyn wrote some time ago - at CPAN we can found 37 modules only for CGI/HTML templates!

Comparation of some modules doing ~identical things sometimes exists in special tutorials or reviews, but you must find these reviews first and most of these reviews in fact incomplete and/or obsolette and explain only one (author) opinion.

I think that CPAN structure must be redesigned (I have no idea about how this can be done now) or at least powered with new indexes.

In last 5 hours I realize one idea about such indexes: Modules Popularity Index. As popularity criteria I take how much results will be found by Google for query:
perl module MODULE::NAME::HERE.
I'm parse http://www.cpan.org/modules/01modules.index.html and then run ~3000 queries on Google. You can see this popularity report (searchable) here.

I think what indexing algorithm must be strongly improved to make this index really usable, but now it interesting too.

Any ideas/comments about CPAN improvement?

In reply to Is CPAN usable now? by powerman

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.


Think about Loose Coupling
	PerlMonks