First thing I have to say is since writing that article (early July time), more things have become clearer. If I was re-writing it now, I'd include a point that PHP lacks a solid set of extensions. Also the remarks on templating systems I'd omit, having understood that PHP is a templating system.
Vincents points are completely correct and I am in many ways, one of those awful coders he complains about (but I'm trying ), having taught myself.
Going back to Jeremy's first post;
The original purpose of the article was not to promote PHP but simply clear up some misconceptions that keep appearing here, in PHP vs ASP discussions. So I agree, it comes across as defensive. Not much I can do about that now. It's not meant to discourage people from looking as ASP.NET at all, just not to swallow the hype when they do so. The article was inspired by some particularily fanatical ASP.NET coders on these forums, selling it as the solution to everything - "even cuts your grass".
This seems like a rather defensive article, taking a "yeah, we can do that too" kind of stance without evaluating how well either technology can do anything.
Otherwise, you commit the number one crime of comparing .NET to PHP. Please re-read Point 1. You then try to back yourself up with this;
First 99% of those extensions require no money and can be dynamically loaded in a script if you no what you're doing (meaning you don't need to pay your web host).
This wasn't meant to be a discussion on just "language.net", as it seems a bit hypocritical to just focus on one portion of .NET, and then be allowed to explain how PHP rocks because of the hundreds of extensions (many of which require $, something .NET doesn't require of you).
Secondly, I mentioned extensions only in point 6 as part of the issue of multi language support.
Here's why you can't compare .NET to PHP. Someone says, hey - PHP won't let you do this, but .NET does!!!
That's invoking an extension, and if PHP has an extension which does this for you (written in C++, PHP or otherwise), perhaps you'd invoke it with;
But that's not part of the PHP language itself.
As to this point about rapid / enterprise development, I think that depends on the developers and the problem in hand. To make remarks like PHP is for "small" is wrong. The fact that many novice programmers are using PHP to get started is no reflection on PHP's scalability. In the hands of an experienced developer...