>>I don't like the idea of working with multi-languages HTML, CSS , javascript, some sort of middle like python, perl, and a web server. ... So if javascript is going to be the language for the near future then why not use it for all the layers. Node eliminates web server, backbone provides the model, and enyo the UI.
>
>Exactly why I started to follow node about 2.5 years ago and pointed that stuff out here about 2 years ago...
>JS is IMO not as nice/clean as Python, but a common language in all layers trumps that - again IMO.

And even for ASP .NET development, the incentive to master JS is great.

Going through John Papa's CodeCamp stuff I hade an "aha" moment looking at his MVVM when I realized the models and view models were js files, not cs and there is really very little C# code in the whole thing. Makes sense, of course, as the UI is HTML/jqueryUI, binding is knockout and he uses qunit for testing, ninject for IOC etc. but I am still new to this and suddenly it hit me that an ASP .NET web api site could rely almost entirely on things other than C#.

My point being that as soon as I looked away from the model of Microsoft enterprise synchronous network desktop applications and started looking at web development two things became obvious :

WPF was not the way to go ( Sivlerlight site is now gone ) as IMO (and I think the opinion of MS right now ) HTML5 / jquery just does it better (and on more platforms) that WPF/xaml .

Javascript is not just a must but a blessing and a lot of fun. Worth every minute I put into learning it with great community and resource available.

Still find the VS 2012 IDE compelling and can easily live with IIS and EF , ( though who knows, after getting my javascript skills up the to the level of my C# knowledge node may become more attractive and I may start shopping ORM alterantives as well ) but it all works very well together and with Razor there are some amazing possibliities for using the strengths of each language.