2 ms·
Assuming that your codebase will continue to be a work of elegance is challenging. Particularly if you're loading CPAN modules that are written and maintained
by btilly 17y ago
Assuming that your codebase will continue to be a work of elegance is challenging. Particularly if you're loading CPAN modules that are written and maintained by other people to a different standard. Of course if you reject those CPAN modules, then what's the point of writing Perl?
But, you say, we'll just limit ourselves to high quality CPAN modules? The real standard ones that everyone uses? Surely nothing will go wrong?
Fine. Last week I ran into a segfault coming from the Template Toolkit triggering a regular expression bug in Perl. (I am waiting on the bug report until I get official permission to submit the patch with the bug. I'm careful about copyright these days...) That's about as standard as you can get. Assume that an extremely popular pure Perl text manipulation module on top of Perl works as documented and enjoy the core dump.
The moral is that unless you are personally writing the whole software stack you're using, you never know what will trigger a bug somewhere. And no sane web company is going to rewrite their whole software stack. (For the record the most painful bugs in the application I described previously were at the C level, and none of that code was touched by anyone in that organization.) However there are architectures that let you mitigate classes of problems before they come up. What is that protection worth to you? Given how much traffic you can get per server, what lengths do you need to go to to optimize?