UPDATE May 21, 2016: The io.js became Node.js and everything is better then ever. Conclusion? Avoid drama, speculations and distractions. Just keep on building useful and good applications.
There have been a lot of buzz around io.js for the past few months. Basically, io.js is a branched (forked in Git/GitHub terminology) version of Node.js.
One of the main reasons to deviate from the main Node.js project was to speed up the development. This way io.js can have more recent features from Google Chrome V8 and ECMAScript6. Those are good things, right? Then, why there has been so many concerns over the future of Node.js/io.js? Why some people were confused and skeptical?
The io.js project is backed by many prominent Node.js contributors. And it gained momentum fast. io.js is already at v1.2.0 and has more contributors than Node.js ever had at any point (as of this writing).
My opinion is that io.js is an improvement. I think there should be more forks! That’s the whole premise of open-source. You can enhance the source code independently.Imagine how things could have been better for Java world if there would have been other maybe less cumbersome versions!
What is your opinion? Have you switched to io.js already? Leave your thought below in the comments section.
2 thoughts on “The End of Node.js?”
I was curious about the version that io.js is managing (1.2.0) and I don’t know if it’s ok, because always told me that when you use the 1.0 release is for a complete stable version, and io.js is not recommend for production environments, or that says in other blogs that I read after this post.
But it’s really interesting, here I found a benchmark with the actual versions of node and io https://raygun.io/blog/2015/02/node-js-performance-node-js-vs-io-js/