I'm giving in this time.
I work in a shop where we maintain (after last count) 112,002 lines of perl in a single system (which also contains about half a million lines of C).
Guess what? It's not a problem! Not in the slightest!
And you know why?
- Coding conventions
- Mature programmers
Two of those three are redundant. Take a guess which ones (the third item isn't part of the anwer set).
If you take a programmer that writes disciplined, careful, extensible, extendable and professional C - are they going to start generating hacked up crap when they switch to Perl? No. They're not. They split source among modules. They use naming conventions. They use strict. They use the namespaces. They use clear syntax. The end result looks almost like C most of the time. Except when it doesn't, 'cause it's Perl.
What does C written by hack-job Perl "programmers" look like?
Rephrasing #37 - "It ain't the arrow, it's the (Native American)".