Use Node.Js Fork & Make Your Own Version of the Project
Since the inception of IO.js fork, the JavaScript community has entirely changed. Henceforth, the community continues to remain volatile. No, I am sure you must have heard about Node.JS including those who haven’t actually used it. The technology brings JavaScript to the server, or to the desktop if you like. It makes JavaScript not just a browser language but something usable in places that languages such as Java, PHP or C#. Being an open source project made it all the more attractive, but at the same time organizations used to face several deep problems which have led to increase in demand for the fork.
Before we proceed further, things to one need to know about io.js:
• Forked out of Joyent’s Node.js v0.12
• Fully compatible with the npm ecosystem
• Will be taking new V8 releases as fast as possible
• io.js is on V8 v4.1.0.14, while Node is still on V8 v3.28.73
• Newer V8 brings in many performance improvements and fixes
• Also, brings in additional support for new ES6 language features
• New (experimental) core modules
• V8: interfacing directly with V8 engine
• smalloc: managing external raw memory allocation/deallocation in JavaScript
• Versioning based on semver, starting with v1.0.0
• Weekly production releases planned
• Bug fixes cherry-picked from Node into io.js as necessary
• Open Governance Model: More power to contributors
My personal take
Till now, io.js has clearly proved that a project can grow much faster with open governance. It has made 10 releases since its first release on 13 Jan 2015!
But the situation is still a bit of a yin-yang! The duality arises from the fact that for every statement that you make supporting the fork, there could be one made opposing it in the same context.
Future says- Node and io.js will unite
With the introduction of such concepts, certain things have become pretty much clear, i.e. nobody wants multiple forks of Node to complicate the decision making procedure. In addition to this, it was never the goal of io.js or node forward to create a second Node.js. And lastly, the effort required to maintain the fork is tremendous.
So those who think that io.js — ‘the friendly fork’, is intended to compete with Node are completely wrong! Perhaps, it is assumed that someday the io.js faction will reunite with Node as soon as there is an agreement on the collaborative decision-making process.
So that’s all for now! For more information and updates keep watching nodejs development company named eTatvaSoft.
