The Origin and Goals of io.js: A Fork of Node.js

io.js is a fork of Node.js that was officially launched at the beginning of this month, with its first version scheduled for release in January 2015.

Fedor Indutny, a core Node developer, together with other core community members, created io.js due to dissatisfaction with Joyent's management and the infrequent releases of Node.js; the project received support from Trevor Norris, Isaac Z. Schlueter, and NodeConf organizer Mikeal Rogers.

The io.js GitHub page describes it as a clone of joyent/node that will be managed through an open governance model, aiming to increase release frequency while remaining compatible with the existing npm ecosystem built for Node.js.

As a brand‑new clone branch, io.js currently has little difference from Node.js, but the technical committee has pledged weekly releases and rapid adoption of newer V8 engine versions, promising substantial changes by the first release.

Node Forward is a community that invites anyone to help improve Node, JavaScript, and their ecosystems; it has shifted its work entirely to io.js, directing contributors there.

Schlueter clarified in an FAQ that neither Node Forward nor io.js aim to compete with Node.js; instead, io.js provides a space for the Node core team to continue improving the platform.

To alleviate concerns about potential fragmentation, Rogers wrote a blog titled “Fragmentation,” arguing that such worries are unnecessary because io.js can attract more active contributors, is governed by a transparent technical committee rather than a single company, and benefits from easy merging via Git and GitHub after Joyent dropped the CLA.

Node.js responded with blog posts highlighting recent progress in open governance, API standards, intellectual‑property management, and transparency, emphasizing community‑driven development while continuing work on v0.12 and discussing future releases.

(Source: infoQ)