A useful article no doubt, but some of the author's remarks in the 'Some real-world issues' section are quite silly e.g.

Perl scripts don't have throwable exceptions. Instead, most Perl programmers use die(...) statements to handle exceptions under the assumption that the script runs from the command line. ...

also,

Perl lacks named arguments for its functions. This is okay for a tight, single file program that is less than 1,000 lines of code, with one developer handling the code for its entire lifetime. But that's not an enterprise reality, and a large ambiguous API quickly becomes frustrating thereafter.