Thank you, Ovid. That helps me position myself, and it clarifies my feelings about the issue the OP raised.

Our code base for this particular project runs in the 90K lines. If I'm generous, I can take 30K off to account for dead code and unrefactored duplication. My feeling was that it's not exactly huge, but not trivial either. Your examples seem to corroborate that.

So, if two fairly competent, mildly disciplined coders can comfortably maintain a code base of that size, it seems entirely reasonable to me to suggest that Perl is quite suitable for big projects. Perl doesn't make it particularly hard to write modularised, well contained code. I don't see why it wouldn't be possible to create huge projects in it that way.


In reply to Re^3: Perl for big projects (what's big?) by rhesa
in thread Perl for big projects by CountZero

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.