But that would create yet another problem. npm has a lot of infrastructure setup so now you have to duplicate all of this infrastructure, get people to adopt your new package manager that's identical to the old one (except has slightly different module support) and move the community to it (or get them to use it in parallel).
I don't think a community of two platforms that are 97% similar with over 145,000 packages can thrive with a fork. Do all 145,000 modules move to the newly forked npm? Do they even have a choice?
I love the ideas behind io.js I just don't understand how it can survive on its own unless it can somehow kill node. I can't see both coexisting for long.
I can't speak for anyone else... but since shortly after the first iojs release, I've been targeting it for all new development. Deploys are moving towards docker based deployment so can, in theory support anything that can be tested on its' own for integration tests.
The bigger thing is that security and critical updates are hitting iojs quickly and following semver, they are not hitting node in a timely manner.
