Andrew Connell

The Past, Present & Future of Node.js and io.js

In the last few weeks I've spoken at a few conferences about using Node.js to build Office Addins, SharePoint Addins & web applications that talk to Office 365 APIs. There's one part in my presentation where I've talked a bit about the status of io.js and Node.js and the future going forward. The skinny is that io.js forked Node.js back in late 2014, they continued down their own paths, but recently they have agreed to merge themselves into a new Node.js. How? What? Why? When? Where? It's a bit confusing, but I stumbled across a really good blog post that explains it for you here: NodeSource - Back Channel Blog - Was This Trip Really Necessary?...

In the last few weeks I’ve spoken at a few conferences about using Node.js to build Office Addins, SharePoint Addins & web applications that talk to Office 365 APIs. There’s one part in my presentation where I’ve talked a bit about the status of io.js and Node.js and the future going forward.

The skinny is that io.js forked Node.js back in late 2014, they continued down their own paths, but recently they have agreed to merge themselves into a new Node.js. How? What? Why? When? Where?

It’s a bit confusing, but I stumbled across a really good blog post that explains it for you here: NodeSource - Back Channel Blog - Was This Trip Really Necessary?

Andrew Connell
Developer & Chief Course Artisan, Voitanos LLC. | Microsoft MVP
Written by Andrew Connell

Andrew Connell is a web developer with a focus on Microsoft Azure & Microsoft 365. He’s received Microsoft’s MVP award every year since 2005 and has helped thousands of developers through the various courses he’s authored & taught. Andrew’s the founder of Voitanos and is dedicated to delivering industry-leading on-demand video training to professional developers. He lives with his wife & two kids in Florida.