> thinking nothing interesting could possibly be done with PHP Sadly, a lot of incompetent developers email each other articles like this, as fodder for dev te

> thinking nothing interesting could possibly be done with PHP Sadly, a lot of incompetent developers email each other articles like this, as fodder for dev team language flamewars. This quoted sentence is likely hyperbole, but they take it seriously and strawman people. (Naturally, language evaluation is multidimensional. You consider alternatives, foresee tradeoffs, etc. PHP can be right/wrong in your situation.) I knew programmers (and their CTO) who trotted out such articles to defend the broken PHP framework which they used to run half the business. I'm sure the framework's own authors would be aghast they still used it. The team working on it had near-zero productivity; virtually all spent maintaining the beast. New hires were flabbergasted at how slow the webapp was, which harmed the productivity of most in the company. One maintainer had a private project to incrementally rewrite the shit in another (very popular) language; the CTO indulged him but refused to support it. (Mercifully, the company got put out of its misery. People might counter that the PHP codebase didn't kill the company. But of course that's not how it works. Incompetence suffuses many such decisions; each of which is just a facet of the same incompetence. And each incompetent decision reinforces the others.)