The io.js TC agrees to:
1. have the io.js project join the Node Foundation
2. rename the entire “iojs” GitHub org to be “nodejs”
3. invite the the current Node.js TC on to our TC to form
the basis of a Node Foundation TSC under the policies
of the Node Foundation
4. moving the io.js Working Groups to be under the Node
I personally preferred the name of "iojs" to "node", but it's true that node's brand is more powerful...
Kudos to whoever made it happen.
Rails became more configurable because of it, but I don't really feel like it ever got smaller or more understandable. That said, I've been out of that game for quite a while, so maybe it eventually did.
But I also don't think it's really comparable because merb wasn't a fork of rails like io.js was of node.js.
Mikeal has more details here: https://github.com/iojs/io.js/issues/1664#issuecomment-10054...
Also great for jsdom (one of node's best features) soon running on node again!
Now we might finally see promises land in Node.js (finally).
They weren't really different implementations anywa - io.js was based on Node and most of the work they had done (as far as I know) was the move to the newer V8 engine version. So they were the same thing, just partially incompatible!
So it's really a great thing that they're merging, because it means that many more people can start actually using the new stuff!
I know there's been a "convergence" repo for a while now, but I couldn't quickly get a sense of how far along that process is.
But seriously, that is a good question. Maybe we can get an answer when node .12 will be stable as well.
Note: this did come up in the TC meeting if anyone listened in. And they are keeping the branding alive and will decide what to do with it in the future.
Make of that what you like.
I think you suffer from a too simplistic view of things.
Their goal is to work on it, stabalize it, and then merge it back in once it's ready for general use. Microsoft's "fork" wasn't trying to split the community or create a permanent new path. It's to build something new for Node.js that shouldn't be in the main project until it's ready. Microsoft wasn't trying to split the community, but rather trying to take on an experimental project.
The io.js/Node.js situation wouldn't have been influenced by Microsoft's announcement. Node.js/io.js didn't necessarily have an intention of reuniting in the future and might have stayed apart. By contrast, Microsoft doesn't intend to split off from Node.js at all.
Whoever else might see this post, I'm sorry, this is just such great news I had to celebrate somehow.
Yeah whatever. Microsoft is no threat to FOS server-side solutions like nodejs, given their reputation. Nodejs is its own worse ennemy.
There will be a Technical Steering Committee in charge instead.
Here's a giant list of people using it: https://github.com/nwjs/nw.js/wiki/List-of-apps-and-companie...
One of the more notable ones is Popcorn Time, the stupid easy to use movie torrent client.
iojs was created a year after Noordhuis's public flogging - that's a pretty slow counterpoint if it was the reason for iojs.
but thanks for the down votes. ;)
from where i am standing i see a lot of ego involved, among other things.