Hacker News Reader

Diverging more, and obstensibly adding more value over the "baseline" node.js, gives the io.js committers more "leverage" in governance discussions. It also arguably reduces the chances of a successful reunification.

Still, it's a good thing overall. There's enough interest in Javascript that demand for a javascript application server isn't going away, and having a headline project that pushes the envelope is a way to keep innovation and interest in the ecosystem.

I hope Bryan Cantrill will do a follow up of sorts to Corporate Open Source Anti-patterns[1] once this is all settled. It would be interesting to know what lessons there are to learn from this.

[1] https://youtube.com/watch?v=Pm8P4oCIY3g

Wouldn't it be better to use io.js as the code base?

Thanks for the info, as an outsider, it is a bit difficult to wade into the long discussions.

Interesting, thanks for the info.