Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Io.js and Node.js reconciliation proposal

github.com

Post reply on HN
Print view View original

11–20 of 83 posts

Re: Io.js and Node.js reconciliation proposal

#11

Post by inglor »

lbotos wrote: post #6
inglor wrote: post #4

Earlier 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.

It still does have a way old version of v8 that's unsupported by Google. For the record.

Re: Io.js and Node.js reconciliation proposal

#12

Post by shadowmint »

keslag wrote: post #9
inglor wrote: post #5

Similar 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.

Given that the Node guys are publicly saying things like 'Io.js, what's that?' I think a little bit of snark is justified.

Re: Io.js and Node.js reconciliation proposal

#15

Post by drawkbox »

Rails and Merb did it (http://yehudakatz.com/2008/12/23/rails-and-merb-merge/).

However io.js seems to be setup the right way here. Javascript development growth is still in massive growth phase. It is hard to prove the singularity exists when paths keep diverting.

I think it is probably healthy to have 2+ or have one win out in the market. Or maybe create others as javascript becomes more prevalent. As the overall javascript development market gets bigger, this will happen more and more. If it gets crazy divergent then standards come about so they work together better. Everything is going to be alright.

Re: Io.js and Node.js reconciliation proposal

#16

Post by xdissent »

inglor wrote: post #4
tbolt wrote: post #3

If 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".

I think you nailed it with "when it's possible." What about when it isn't? They're clearly divergent projects, so now you have to keep track of whether every npm package you use supports Io or Node, and which version of each. Package authors are now responsible for supporting one or the other, or becoming an expert on the differences in order to support both. It's a crappy burden on all parties involved.

Re: Io.js and Node.js reconciliation proposal

#17

Post by pekk »

BinaryIdiot wrote: post #8
simplyluke wrote: post #2

I 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.

They have to merge otherwise one will die. There is no alternative. I hope it happens sooner rather than later.

Multiple languages coexist. Within Javascript, there are multiple module systems, general utility/polyfill libraries, test runners... for better or worse, we continue to have many alternatives for almost anything. So why not also different implementations of a language interpreter?

Re: Io.js and Node.js reconciliation proposal

#18

Post by xdissent »

pekk wrote: post #14
[deleted] wrote: post #13

[deleted]

That doesn't make any sense to me. If Node is good enough, or io.js is good enough, then they are no better if the other stops existing, and no worse if the other continues existing.

But both require a healthy ecosystem of packages to be any good at all. Right now the existence of io is making package authors choose to support one or the other or do the extra work to support both. Node is getting worse for that. It's a little less of a worry now that node 0.12 is out, but the politicization of the split is just going to make developers choose sides and focus their efforts on one or the other. And considering the fact that both use NPM for package distribution, package management is going to get more difficult, not easier.

Re: Io.js and Node.js reconciliation proposal

#19

Post by baudehlo »

inglor wrote: post #5

Similar thread on NodeJS's GitHub. Booming with comments and interesting discussion as usual ;) https://github.com/joyent/node/issues/9295

Why would people comment there though when the issue even points out that the discussion is on the io.js issue? Seems rather petty.
Post reply on HN