I happen to love perl for getting quick, one-of, temporary jobs done very easily, but if you really want perl to have corporate use for real long term projects, you are bound to run into people like me who wouldn't touch perl for production use with a ten foot pole (sorry :-).
Perl really is a write-only language, and you just can't do production work write-only - someone has to maintain production code, and the language is so fantastically huge, no two programmers even appear to be writing in the same language.
I'm not sure what feature you could deliver to address this problem, but there's your first challenge :-).
I don't know who this Tom Horsley is (and I'm not sure if I would like to find out or know what his status in the Perl world is) but clearly it is someone who hasn't been keeping himself updated on "modern" Perl modules (e.g. Catalyst) and seemingly hasn't ever written a decent module, program or script. If he is the same Tom Horsley as who has written the Tom's fabulous web Page then I understand why he thinks Perl scripts are not really production grade, since the few Perl scripts he has on this site are indeed not prime examples of well written Perl.
Whatever language you write in, your task as a programmer is to do the best you can with the tools at hand. A good programmer can overcome a poor language or a clumsy operating system, but even a great programming environment will not rescue a bad programmer. Kernighan and Pike
(The C programming language) is a razor-sharp tool, with which one can create an elegant and efficient program or a bloody mess. Kernighan and Pike
Really it are people like Tom Horsley who negate all efforts to promote Perl by uttering such unproven, unfounded and unconsidered nonsense. If I could post on perl5.porters I would tell him myself, but on second thought "Don't feed the trolls".
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law