| From their front page: > io.js is an npm compatible platform originally based on node.js™. Sorry, they were aiming for 100% tests passing [1], I would assume for npm compatibility which is their primary goal. A stable API means that dependent packages don't have to change to stay compatible. Tests are failing because they change things that broke packages: * Node-inspector does not work with io.js! How is anyone supposed to debug their code? [2] * Fibers do not work [3] * msgpack does not work [4] * sqlite3... there is a long list [5] There is no CI, no debugger, tests aren't passing, major modules don't work. I absolutely cannot go to my CEO and make a bet on that for my company. I think io.js is great! But the amount of misinformation about the state of Node is staggering. Let anyone with proof otherwise also cite their sources. [1] http://blog.izs.me/post/104685388058/io-js [2] https://github.com/node-inspector/node-inspector/issues/523 [3] https://github.com/laverdet/node-fibers/issues/203 [4] https://github.com/msgpack/msgpack-node/issues/20 [5] https://github.com/iojs/io.js/issues/456 |
Node 0.12 was released and ships with v8 3.28.73. Most (if not all) of the bug reports you cite refer to needing NAN 1.5 which fixes issues with v8 > 3.28. NAN is used by both io.js modules AND node.js modules.
Both io.js and node.js 0.12 have a v8 > 3.28. All those modules are also broken in Node 0.12 because the underlying v8 API changed.
As pointed out by others, the node.js tests are only passing because some last minute shenanigans so they could claim all their tests were passing "but io.js' tests are not."