It's funny 'cause it's true
I've once seen an app written in VB -almost exclusively macros, if you ask-, backed up by... wait for it... excel spreadsheets for data management. PHP was but a foetus at the time, but I'm sure the *erm* "developper" responsible for this has now *erm* coded a couple web interfaces -in PHP- for his various VB masterpieces. It might sound a bit extreme, but go have a walk around the web and it won't sound that extreme anymore...
Funny how people keep saying "PHP is great if you know what you're doing". NOPE. PHP is a piece of smelly swine waste, _because_ it allows for the sloppiest coding practices known to Man. Also, Perl sucks moose balls and Java is for sissies, if you ask me, but PHP clearly gets the "dumb queen" crown -OK, make it a draw, after all there _are_ VB programmers around.
And that's because of the first and only Rule in the IT world, from which all the other can be derived: when you design a tool that *can* be used in a clueless way by braindead morons, you know it *will* be used in a clueless way by braindead morons. Especially if you give them an automated tool to commit their atrocities.
Now I must admit that it's probably possible to write a coherent piece of PHP if you really want*, but if you have the skillz, why not use a real language? Back to The Rule: when you have real languages on one hand, and PHP in the other, you know the real coding will be done in a real language, while PHP will be used to build piles of hacks upon hacks upon hacks (skyscrapers held together with duct tape, as a previous commenter rightly typed).
The article is quite funny too.
Now for the article's downsides: where the feck are the fracking "f*ck"s? Also, the proposition "which means they both fail at failing." is a failing fail. Should have read:"which means they both fail at fail".
*purely hypothetical, I doubt anyone ever tried