3 ms·
Given MSFT's history of doing their own thing rather than supporting the community alternative, this seems like a really strange decision; particularly as they
by hugorodgerbrown 15y ago
Given MSFT's history of doing their own thing rather than supporting the community alternative, this seems like a really strange decision; particularly as they have the potential to build a great competitor product using .net async features (http://lorgonblog.wordpress.com/2010/03/28/f-async-on-the-server-side/ http://lorgonblog.wordpress.com/2010/03/28/f-async-on-the-se...).
Building JScript in parallel to JavaScript back in the 90s was a dumb idea, but forgoing their own toolset to support node.js is equally misguided. They should concentrate on educating .net developers on how to compete with the non-msft development community using the .net platform to bring them to productivity / toolset parity, and fostering open-source .net projects.