Age in and on itself isn't an indicator of quality. It's true that development in old projects can slow down[1], but this is by no means necessarily true, and young projects in turn can be lacking, e.g. in maturity, code quality, features and so on. I'd advise against judging projects by their age.

Perl 5, for what it's worth is undergoing active and exciting development; just check the perldeltas for the latest versions.

I also feel I should take up the cudgels for CPAN. You talk about CPAN as if it's a bad thing, but the opposite is true; CPAN is an extremely valuable part of the Perl ecosystem. CPAN allows you to (fairly) easily share the fruits of your labor, and benefit from others' in turn; as such CPAN is a large part of what has made Perl a community, rather than just a language.

Sometimes there's several competing modules on CPAN, but that too is a good thing. After all, isn't TIMTOWTDI (There Is More Than One Way To Do It) one of Perl's mottos? Competition is good, and the best solution will eventually win out. In fact universally-useful, well-maintained CPAN modules can be bundled into the Perl code, and are.

And if no module wins out, and if different people keep on using different modules, then those modules obviously fill different niches. There's room for more than one module for any given task on CPAN anyway, and people being able to scratch their particular itches and getting their jobs done with a minimum of fuss is what I'd call a success.

  1. Whether that is a sign of stagnation, or simply conversion on the "Golden Code", is another question as well. TeX (i.e. core TeX itself, not the surrounding ecosystem) is perhaps the best example of the latter, a project that's not seeing much development anymore because it's approaching perfection.

In reply to Re^3: What's the perl5's future? by AppleFritter
in thread What's the perl5's future? by xiaoyafeng

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.