Cool, but how does it make the claim that .NET (and .NET alone, since he's singling it out - not even Java is getting the same treatment) is "cookie cutter technology"?
I'd say because, in general, Java is NOT cookie cutter technology. One of the big complaints coming out of the .NET camp is that Java just has too many options, that you'll spend more time deciding which technology, library or framework to use than doing actual work.
So in a way I agree with what he says, because from experience I can say that I have met my share of .NET developers who think that a Web Service is that option that appears on the menu of Visual Studio and have no idea how all of it works or how to make it behave differently from the given defaults.
Now, you'll find brilliant people doing .NET and useless ones doing Java, but the moment they put on their CV that they know how to handle a certain technology I can be more or less sure that the Java developer at least read the documentation because most likely there wasn't a button for it on the menu of his/her IDE.