Clients want mainstream platforms, especially corporates. They've all been burnt in the past at some point by becoming reliant on key applications that turn out to have been developed by some guy who was a one man genius in perl or lisp or something and now that he's emigrated/retired/dead they find that either there's nobody with the skills to leverage their old code or the skills are rare and very expensive. The more mainstream your platform, the more supportable and future proof it will be, and the simpler your life will be when you have to maintain the code in two years time.
An article like this that blithely condemns anyone or anything to do with .NET is just plain stupid and speaks volumes about the author's prejudices and lack of insight into both the .NET platform and the development environment in general. It's the kind of dogmatic garbage that makes for an eye-catching article and not much more. McDonalds is one of the most successful companies in the world precisely because it is so standardized, sytematized and simple to operate - it produces results, efficiently, consistently and predictably. Why are these bad things in a development environment? They are exactly what we should be aspiring to as commercial developers.
I've seen a huge amount of projects go south because, for example, the client wants a simple online order/invoice system that can be banged out in ASP.NET in two days, but some self opinionated so-called hotshot developer decides the project must be some multi-tiered overcomplicated system with an Adobe AIR front end and a backend processing system in C++ and with data held in some convoluted XML format on a nosql distributable database, because "these are the best tools for the job". Six months later the client still doesn't have a working solution, but never mind because the interface is beautiful and the data model is a work of art.
Completely agree. This author, to put it politely, is an idiot. I hope he never uses object orientation or design patterns since those ideas fall into precisely the same trap - they are designed to enable solutions to be churned out more quickly, relying on the idea that a lot of solutions comprise similar components, like a Presenter, or a Repository. This leads to easier development, easier unit testing, faster development, easier maintenance and likely lower costs and risk for everyone involved. Its pretty much the same with .Net itself - it can allow you to do more in a short space of time precisely because MS had a look at what most people do, and realized it could speed these things up.
I'll bet he gets all of his coders to code in vi or vim because its "better" the old fashioned way.