4 ms·
As far as I know (I'm quite new in Node), io.js wants to join the ES6 pretty soon, and most of the developers have gone to io.js from Node.js. So, while there m
by franciscop 12y ago
As far as I know (I'm quite new in Node), io.js wants to join the ES6 pretty soon, and most of the developers have gone to io.js from Node.js. So, while there might not be a big enough difference right now, if they continue separated there will be soon enough.
- sigzero 12y agoDivergence is what we are worried about. I am hoping they come back together with the io implementation being the bleeding edge going back into node stable.
- iends 12y agoio.js isn't very bleeding edge though. That's just FUD.
- franciscop 12y agoNot so sure about that being the best way. I agree that it would be the best for not confusing short-term. However, there are also many problems with that approach, mainly that Node.js is not of the community, it is from Joyent. While this works great in some cases (Linux), there were apparently many problems with Node.js. I think the best would be: 1. Joyent giving the name to io.js so they can keep developing Node.js at a fast speed while keeping the name to avoid confusion. 2. As 1 is highly unlikely, IMO the best next thing is for io.js to gain market and popularity as fast as possible.
- malandrew 12y agoHuh? No, io.js is a fork of joyent/node by many original core contributors. io.js has more es6 support since it's based on a newer version of v8. Development on joyent/node slowed to a crawl and now the NodeFoundation is begging the io.js developers to return. If things remain separate, joyent/node will probably not progress much more and eventually everyone will view io.js as the "next" version of node.