CPAN is stuffed with great, good, bad, and terrible code all mixed up together; there’s no consistent standards for versioning, there’s no consistent standards for coding; like Perl, there’s little, if any, consistent standards.
And that’s why it thrives. If it tried to enforce any of these to any extent, it would wither, like the repositories of other languages have.
PEAR, at the very least, is a wasteland. Ruby’s Gems thingie is doing better… but is orders of magnitude smaller than the CPAN. I don’t think Python has anything resembling any of these. Java’s central repository is called “Google” and the quality of stuff is all over the place – certainly less consistent than CPAN with its lack of standards… although the high-quality Java libs are consistenly good and well documented (though that barely makes the language any less unfun…). We’ll see where the JSAN goes – being a bit of an outlier in this set as it is.
Certainly I’ll take the CPAN over any of those.
Makeshifts last the longest.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||