I argue that Perl suffers from "Too much of a good thing."

What evidence of this "suffering" do you see? Are people leaving Perl in favor of languages with fewer options, for that reason? Frankly, I would have left Perl long ago if not for CPAN, and I think CPAN doesn't "suffer" from this condition - it florishes because of it! Perl makes hard jobs easy because we all get together and put our best work on CPAN. If we decided we only wanted X config modules or Y template modules we'd run a very high chance of missing out on something great! Sure, there's a price in user confussion, but I think it's a very small price to pay for the gigantic boon of a healthy, vigorous development pool.

Certainly each option is a good solution for a specific kind of situation, but how do we know *which* module works for *this* solution?

Easily done. Just read Perlmonks - we're all more than happy to state our preferences when we're asking for help or answering questions. Of course that will never be enough to guide your choice alone - you'll have to do research yourself and take risks. Then report back and let us know how it went.

-sam

In reply to Re: On the scaleability of Perl Development Practices by samtregar
in thread On the scaleability of Perl Development Practices by jdrago_999

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.