Here’s the blurb from the Github io.js Readme file on the project:
We intend to land, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for node.js.
The feeling among the io.js contingent seems to be that Joyent’s move in October to set up a Node.js Advisory Board came too late to settle differences in how the project is managed. Infoworld’s Paul Krill interviewed io.js contributor Mikeal Rogers about why the group went this route.
No one can say this is a surprise. There’s been angst in Node.js land at least since late last year when a spat erupted between two top Node.js contributors, which caused considerable bad feeling.
Talking to media, Joyent CTO Bryan Cantrill downplayed concerns that the dual projects will lead to fragmentation and said Joyent has reached out to the io.js team.
The stakes are high. Node.js has seen great traction in companies including [company]LinkedIn[/company], [company]PayPal[/company], Uber, [company]Yahoo[/company] and [company]The New York Times[/company].
Presumably, none of these Node.js players want that momentum to stall.
Photo credit: Jakub Mosur