Node.js vs. io.js
It’s our opinion that a wait and see approach is the most pragmatic. First, there are two possible paths forward for the fork:
Let’s address point 1 above first. We think a re-unification is the most probable outcome. Assuming a merge of Node.js and io.js is imminent, then it makes no sense to switch to io.js.
First, the current release of io.js has some nice new features, but not enough to cause 51 of every 100 companies/developers that use Node.js to switch. Further, if io.js releases new capabilities that are truly compelling, then we would expect the Node.js camp to quickly adopt those features to ensure it does not fall behind.
Third, due to the first two points we think its unlikely that greater than 50% of developers switch to io.js.
Did we mention that we think Node.js and io.js will be unified into a single project again. Whether or not were are right, we still think a wait and see approach is best where new projects target Node.js for now.
Wide spread ES6 adoption and usage will likely occur in parallel with full ES6 support in the main browsers.
We specialize in helping professional developers, like you, expand your skill set. Our courses are focused on enabling you to learn everything necessary to use a new technology in a live, production application.
All courses are made with love in
Palo Alto, CA.
Subscribe to our newsletter