I read the list of new submissions to CPAN on a daily basis. I have found it impossible to get authors to add related modules to the SEE ALSO section of their docs. Sometimes they don't respond. Sometimes it is egotism. Sometimes I just don't know. But the bottom line is that there are a lot of modules related to each other that people don't know about.
The ideal solution would be to cobble up a database and render HTML from that , but i am too lazy to do it.
Also, one needs to distinguish between
- plain jane lists of modules
- Here
is my list of modules for lazy loading. It is nothing but a list, with no attempt to feature-compare. Ok, there's a bit of feature-comparison, because I draw a line between modules which only do lazy loading and modules which offer lazy-loading as part of a larger functionality-base.
- lists which make comparisons of features
- Here is where simonm makes a feature comparison of various DBI wrappers. It is an example of not just blindly listing things, but attempting to make a comparison of them.
We can probably also place choosing a templating system by perrin in this category
Aristotle's
A brief survey of the DBI usability layer modules on the CPAN also falls into this category. as well as tphyahoo's survey of surveys of templating systems
- reviews based on use cases.
-
These are usually submitted to the Perl conference or YAPC::NA. They are very useful but time-consuming. for example, I have developed DBIx::Recordset::Playground which gives runnable code sampls for using DBIx::Recordset, but I cant imagine getting the work for 3 or 4 related modules done as well. I was happy in a thread I created long ago to have autarch submit some Alzabo code to compare with how other DBI wrappers would do the same thing.
Concluding, I am mainly interested in a place to develop blind lists and perhaps having the follow-ups relate personal-experience or feature-comparison.
If you notice, there is an ever-growing set of off-site links from search.cpan.org for each module - AnnoCPAN, CPANForum, CPANTesters, CPANreviews. It seems to me that CPAN-related is a gap that could be filled by a section of this website. What do you think?
-
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.
|