1 min read
on Jan 29, 2015
We haven’t gotten around to updating this post just yet
As you read on, keep in mind that while some information may not be completely up to date, this article still contains some useful insights.
In this talk, Mikael Rogers discusses io.js including the reduction in Node.js contributions and the difference between Node.js and io.js.

io.js began with a large concern over the lack of contributors to node.js. Node.js benefits from a vibrant community, but contributions to core repositories have declined, suggesting that the future vitality of the community may be at risk.

io.js vs node.js

Node.js contributions

The Emergence of io.js

Thus the emergence of io.js, a fork of the original Node.js JavaScript evented I/O runtime. io.js is created under an Open Open Source, which promotes a broader, more open contribution to the core repositories.

Open Open Source: individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

In the talk below, Mikeal Rogers, an io.js contributor and TC member of the project discusses io.js in more detail including the reduction in Node.js contributions, the differences between Node.js and io.js, and moving the JavaScript community forward.

io.js vs Node.js from PubNub on Vimeo.

More From PubNub