Re: Node.js vs. MS .Net Web Application Development

In case you didn't know, .Net can be used to develop desktop apps, web
apps, web services, etc.

That seems to be causing a catch-22 situation for Microsoft. You're danged
if you do, and you're danged if you don't.

If you build a business model around controlling the technology stack from
the database to the user interface and everything in between you create an
expectation of delivering a homogeneous framework.

But the homogeneous framework goes out the window as development paradigms
shift. The framework get's splintered between Microsoft and non-Microsoft
parts.

Then Microsoft adds more to its framework in a frenzy to be all things to
all people. Then developers complain about the framework becoming overly
complex. They ask, why does my IDE offer me templates for 10 types of
"projects" if all I want to do is 1. Why does it offer me 8 ways to manage
user state? Why am I paying for all this infrastructure that I don't need?