Io.js and Node.js reconciliation proposal
1–10 of 83 posts
Re: Io.js and Node.js reconciliation proposal
#2Re: Io.js and Node.js reconciliation proposal
#3Re: Io.js and Node.js reconciliation proposal
#4If these projects don't get merged, it's going to be a shitshow in my opinion.
io.js can certainly benefit from these fixes but I don't think it'll be a "shitshow".
Re: Io.js and Node.js reconciliation proposal
#5Re: Io.js and Node.js reconciliation proposal
#6If these projects don't get merged, it's going to be a shitshow in my opinion.
Why? io is more stable and fixes get backported to node when it's possible to backport them. io.js can certainly benefit from these fixes but I don't think it'll be a "shitshow".
Re: Io.js and Node.js reconciliation proposal
#7Earlier quoted context omitted.
Why? io is more stable and fixes get backported to node when it's possible to backport them. io.js can certainly benefit from these fixes but I don't think it'll be a "shitshow".
isn't the reason io was formed because node was so outdated? It had a way old version of v8.
Re: Io.js and Node.js reconciliation proposal
#8I really hope we can see a unification of the efforts and work through the political issues. Having very talented developers working on separate codebases instead of improving one seems counterproductive.
Re: Io.js and Node.js reconciliation proposal
#9Similar thread on NodeJS's GitHub. Booming with comments and interesting discussion as usual ;) https://github.com/joyent/node/issues/9295
Re: Io.js and Node.js reconciliation proposal
#10Similar thread on NodeJS's GitHub. Booming with comments and interesting discussion as usual ;) https://github.com/joyent/node/issues/9295
Well, considering the issue was created 6 minutes before you posted this comment, this is facetious and disingenuous.
Check out the other top 5 issues - it's mainly a bunch of people talking to themselves.
Anyhow - I genuinely wanted to link to both - not trying to poke at node.