I don't agree that the diversity of CPAN is a drawback of Perl. On a slight tangent to this discussion, one thing I would like to see is a better organisation of CPAN. e.g. if I want a web-based templating system, I'd like to be able to browse through some categories, drill down into web, and find a list of templating systems that might suit my needs. If it was linked into ratings, reviews, annotations, etc. even better.
In case there's already a site that does this (it wouldn't suprise me), I'd like to add that this functionality should be built into CPAN, so that it's something people will use automatically, rather than after they've been playing around with CPAN for a few months, and managed to find a link somewhere, or ask the right question on PM. The categories, etc. would also need to be maintainable by people other than just the module authors.
As I said, I think varied options in modules is a strength of Perl, and is something many other languages have (actually, Perl is one of the most diverse in this area). I just think this strength needs to be taken full advantage of.
-
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.
|