The Future of Node Is in Microsoft’s Fork
&gt; The future of Node is in Microsoft&#x27;s fork<p>People should read &quot;Embrace, extend and extinguish&quot;: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Embrace,_extend_and_extinguish" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Embrace,_extend_and_extinguish</a><p>It happend with Java. Microsoft created their own slightly improved Visual J++ and then Visual J#, and after Sun sued them and MS had to remove their proprietary MSJava from WindowsXP, they forked it with C# 1.0).<p>It happens with JavaScript. They tried to kill Netscape (Browser Wars) with their powerful but slightly incompatible JScript. Remember the IE 6 problems, it&#x27;s the result. The XHR&#x2F;AJAX came out of these era too.<p>It almost happend again with JavaScript. First they tried it with JavaScript 4 that never got mainstream (tried to added classes and XML syntax). Thanks god JavaScript 5 came along as lean barely changed succesor.<p>It happens again with JavaScript &#x2F; ES6&#x2F;7 and TypeScript. They lobbied to add &quot;class&quot; syntax and at the same time create an competiting language on top of ES6 (optionsl typing, like HACK does for PHP).<p>It happens with Node. The plan to release (we heard that often from MS, it my take a while...) their JavaScript engine and forked Node.<p>Please wake up, and learn from the past history of Microsoft. They are not saints and judge them by their past actions and also their recent Windows 10 forced phone home and forced update disasters, the expensive license changes, etc. I am certainly happy as long as the official Node will continue to run on V8 on all platforms.