It’s well known that PHP is a dead programming language and that its 22-year-old ecosystem is effectively useless now that we have Node and its fancy new asynchronous frameworks. Node’s superiority is evident because everyone knows that single-threaded, asynchronous, programs are better by default. Faster. Stronger, even.
“But Simon! Why?!”, you’re probably yelling at your MacBook screen. Here’s why:
PHP developers are not in demand at all. After ~22 years, all companies using PHP immediately gave up on it as soon as Node v0.0.1 was released because it was instantly the better application environment. Furthermore, everyone knows that to be a successful new startup (unlike Slack) you have to create Node-based web APIs backed by MongoDB. It’s simply impossible to be successful otherwise.
Here’s some science to back up these claims.
The ecosystem surrounding a language is probably the single most important factor in deciding not to use it. Luckily for us, PHP has been around long enough that its ecosystem is full of large, well-maintained, and full-featured frameworks to hate like its Rails-equivalent Laravel or its enterprise frameworks Symfony and Zend. Unlike PHP, Node developers don’t have to worry about finding a framework to hate because everyone just writes their own. By writing their own framework, a developer can truly separate themselves from their competition by reinventing the wheel in a way that makes sense to them. This practice also doubles as job security for the developer, as seen in the Scientific™ Job Prospects research results above. It also triples as Developer Cool Factor™ (all great developers write their own frameworks, check out Magic-Box or MortarJS).
The overwhelming evidence for Node’s superior ecosystem can be witnessed below.
Of course, a developer’s true level of productivity can only be measured in how they spend their time. Seen here, PHP developers waste more time writing code and building functional applications than they do cultivating Developer Cool Factor™ mass and GitHub stars. This is obviously going to reflect negatively on them when they apply to work at a startup and is thus an unproductive use of their time because, as we all know, GitHub stars are a quantitative way to measure developer skill.
PHP developers’ inability to contribute to society is made obvious below.
Things You Can’t do as a PHP Developer
- Legitimate asynchronous programming
- Get consistent, easy to use function parameter ordering for standard lib functions
- Build your own React TODO MVC app boilerplate
- Server-side rendering with a front end in-browser framework
- Create your own memory leaks
- Make whitespace significant
- Leak data between requests
- Solve world hunger
- Tell people you’re a PHP developer
PHP as a Business Tool
We all know that PHP is unquestionably inferior and cannot support a legitimate business’s application, so here is a list of failed businesses using PHP compared to a list of successful businesses implementing Node-based web services.
Every developer knows that the quickest and most efficient path to getting anything accomplished is to complain a lot and start from scratch. The market will always wait for your startup to finish building its framework first. Besides, why should we bother to offload work and rely on a language’s open source community when we can just do everything ourselves?