Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I though the whole point of io.js was that they would work on the project faster than Node, but eventually merge back into Node once Joyent became more transparent. The Node release cycle was pretty slow and they had some dispute with the contributors (top 5 original Node contributors now working on io.js)


I would not think the merge back is going to happen. The longer they separate, the more unlikely (and apparently harder) for them to merge


Why would the io.js team bother merging their changes "upstream" to Node? io.js has momentum and mindshare.


They publicly stated they will merge back in upstream eventually all being well. They're doing it for the good of Node.js, not to create a rift and divide the community's efforts.


IIRC the Node Forward initiative was more explicitly focussed on merging back than io.js is. The subtext of io.js seems to be "we'll move forward with or without Node moving foward with us".


Yup. Also because Joyent asked that Node Forward not use the "node" term, even though it was in public domain a lot longet than Joyent's been around.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: