Not 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.
Comments
Not 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.