|laziness, impatience, and hubris|
Perl and Infiltrating PHP Workplacesby Withigo (Friar)
|on May 23, 2006 at 22:18 UTC||Need Help??|
Like many monks before me, I am presently wrestling with alluring temptations(i.e.,actual job offers) beckoning me to turn away from the path of the righteous(TMTOWTDI) and do PHP coding.
But man cannot live by bread($$$) alone.
I am wondering if any of you could share any of your successes of starting at companies who are either doing significant work in PHP, or moving towards being locked into PHP, and being able to covertly replace PHP with Perl over time. Or instead of covert-ops, perhaps getting to be on the company's elite-Perl-ninja squad. It is a truism that many companies have no idea what technologies they ought to optimally use, but instead just use whatever is marginally compatible with their current systems, as setup by previous architects and administrators, or even worse use whatever some fast talking salesman in a suit sold to upper management.
PHP is easy to learn, but has a shallow pool of potential problems for which to provide a solution(die CMS/AJAX frameworks, die!), while Perl is beastly complex and arguably has a stated goal of being infinitely extensible(via Parrot). Those latter virtues of Perl are often deemed to be the gravest of vices in the eyes of the uninitiated(i.e., the unintelligent), and so PHP is chosen for being faster and cheaper("good" is no longer even an option).
I would be especially gladdened to hear any war stories about PHP failing to meet some need which was eventually done(right) in Perl. (Bonus points for stories in TheDailyWTF.com tone.)