Earlier quoted context omitted.
Yeah, Mono was at least realistic in the last year(s), but it was always a bit of a guessing game whether something was going to work or not. Having an official linux/mac os ASP.NET will be huge, even if the functinoal difference is minor compared to Mono. Just knowing it will work tomorrow , and after the next major release is huge. Yesterday I would rather have chosen Node.js than a .NET solution for a small servic…
Node's like, one of the worst choices, due to the idiotic package manager. They ship essentially every function call as a separate package. It's actually a thing to take a dependency on "sha1" and literally pull in a package just for that one bit. Using Node/Grunt/Bower to build a straightforward run end site (just to compile static outputs) required npm installing over 13 thousand files. Now imagine on a build serve…
I love yeoman, great scaffolding tool, but it depends on so many packages that sometimes it simply doesn't work because some package it depends on did something silly. So once you have a working set up, don't update it if you absolutely must.
That shouldn't be the case in 2014.