Popular open-source contributor to framework programming, Node.js, has recently been split into two separate projects.
The ‘forking’ event, as they are calling it, has resulted in the creation of another rival open-source framework ‘IO.js’ version, apparently, brewing up ever since Joyent started steering Node’s ship of projects. This retaliation of developers against the one ruling them has undoubtedly taken Joyent, Node’s corporate supervisor, in for a surprise. But, a declaration from Isaac Schlueter, one of the rebels, which states that by no means is IO.js meant to overthrow Node.js and that someday, after the issues are settled, the fork shall merge into one, has calmed down the storm evidently.
As of now, here’s what you need to know about the fork and IO.js:
What led to the fork, in the first place?
Of course, the rebellion didn’t happen overnight. Top Node contributors were already bittering about the way Joyent was complicating the project and making it sloth. The decisions the company was making, weren’t working well for the platform. Further, the contributors were already dissatisfied with the fact that they had no control over the project or were side-casted as least important beings when it came to decision-making. Although Joyent understood the unhappiness of the dissidents very well, it never did anything to control the unrest. And what resulted eventually, is known to all.
Who was behind the counterstrike?
Fedor Indutny, a member of the core team at Node.js is believed to have started the war. A technical committee for that matter, was formed, which was joined by Trevor Norris, another core team member, Isaac Schlueter, an ex member of the core team, Ben Noordhuis, another alumni and Bert Belder, an alumni turned maintainer at Node.js. Rod Vagg, a Node.js devotee, was also into the game, somewhat. He has taken part in creating and managing the build. Mikeal Rogers, a supporter of the fork, on the other hand had moderated all meetings held by the technical committee and helped in building the agenda.
What is this latest IO.js? What does it do?
Know IO.js as the fork that bifurcated from Node.js, as of now. It is a split-up of node v0.12, the stable, unreleased version of its parent. The nascent framework is believed to be entirely compatible with its parent framework. It carries the work that was earlier done on Node Forward repository by Fedor Indutny.
At present, there’s no news whether IO.js will be dissolved after the issues are settled. As a matter of fact, the contributors are interested in merging both frameworks and also in maintaining each of them individually. Rumored to make its debut on the 3rd of January, 2015 (Indutny’s birthday) the platform is undergoing rigorous processing to enable timely following its launch. To put it in a nutshell, IO.js is a Node version upon which releases, contributions and contributorship – everything is under an open governance model.
Although the dissidents claim to stay Node compatible, this fork can have more adverse effects than we can ever imagine. The success of the two entities will entirely depend on the individual preferences of software companies. With reactions like Uber’s recent tweet stating how it wants to opt for IO.js, the guiding stars for Node do not seem to be shining much.