Barring a merge back into node.js (which could still happen), I don't see myself going back for new projects.

For one, it's a fork, not a new product -- so it carries all the old development from node.

Second, it got all the best contributors from the node community.

So, while it might not be a standard yet in numbers, it's very well poised to be.

As far as "big sites", several are starting to roll out io.js deployments. Most places don't blog about every upgrade to every internal piece of infrastructure. If you're doing the SOA thing properly, you can start rolling out io.js for new services without removing the versions of node used for other stuff.

At npm, we have some io.js, lots of node 0.10, erlang, java, spidermonkey, python, redis, postgres, etc. It's pretty common to use different stuff side by side in little servers that talk to one another. Less dramatic to talk about than pretending your'e gonna make some big switch-over though.

You don't see many people using `node.http.cat()` any more, for example. And yet the community survived ;)