IO.js – Evented I/O for V8 javascript

Can someone tl;dr me the gist of everyone's beef with joyent? I've been hearing about a fork but haven't understood / seen why people feel like the fork is necessary.

Node is the obvious leader amongst V8 shells, but there&#x27;s also<p>- <a href="https://github.com/attractivechaos/k8" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;attractivechaos&#x2F;k8</a> and discussion <a href="https://news.ycombinator.com/item?id=7913950" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=7913950</a><p>- <a href="http://silkjs.net/" rel="nofollow">http:&#x2F;&#x2F;silkjs.net&#x2F;</a><p>- <a href="https://code.google.com/p/teajs/" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;teajs&#x2F;</a><p>- <a href="https://github.com/samlecuyer/sorrow.js" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;samlecuyer&#x2F;sorrow.js</a><p>- <a href="https://github.com/tlrobinson/narwhal" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tlrobinson&#x2F;narwhal</a><p>- d8 (bundled with v8 source)<p>Not counting other CommonJS-compatible platforms, or javascript shells using engines other than V8, or server-side javascript application frameworks

From my Twitter feed...<p>&quot;Looks like a Node.js fork called io.js is happening, with some of Node&#x27;s key contributors. 😮 <a href="http://github.com/iojs/io.js" rel="nofollow">http:&#x2F;&#x2F;github.com&#x2F;iojs&#x2F;io.js</a> &quot;<p><a href="https://twitter.com/devongovett/status/538131893682569216" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;devongovett&#x2F;status&#x2F;538131893682569216</a>

Wahoo, hope people are more open to change this time around – hope it works out!

40 minutes, 8 points, got to the front page, and... why? Is there a story behind this fork?

It&#x27;s raining node forks: <a href="https://github.com/io-forward/io-forward" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;io-forward&#x2F;io-forward</a>

I&#x27;m finding the situation with Node.js quite frustrating. There doesn&#x27;t appear to be much communication as to what&#x27;s going on with the project.<p>It&#x27;s also odd that the Node Advisory Board was supposed to meet on the 20th (2014-11-20). Chris Williams tweeted that it was about to start [1] but no minutes have appeared and I can&#x27;t find any mention of what happened during the meeting.<p>[1] <a href="https://nodejs.org/advisory-board/2014-11-06/minutes.html#minutes_md_next_meeting" rel="nofollow">https:&#x2F;&#x2F;nodejs.org&#x2F;advisory-board&#x2F;2014-11-06&#x2F;minutes.html#mi...</a>)

With what purpose? What&#x27;s the significance of this? node is also node with many of the key contributors.

@Mikeal has a couple of posts on the subject:<p>- <a href="https://medium.com/@mikeal/on-corporate-ownership-of-open-source-786ebd15847e" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;@mikeal&#x2F;on-corporate-ownership-of-open-so...</a> - <a href="https://medium.com/node-js-javascript/fragmentation-7e87d28f60fe" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;node-js-javascript&#x2F;fragmentation-7e87d28f...</a>

10000+ commits and 574 contributors. Boy, this has to be good. Can somebody explain?

I think it comes down to politics, I feel its always better to have a company run and support an open source framework as long as their listen to the community and letting the community be a part of the framework.

If you are curious about node-forward vs io.js take a look at the end of this page <a href="http://nodeforward.org" rel="nofollow">http:&#x2F;&#x2F;nodeforward.org</a> to see how they are related :-)

As a dev do we continue to use node or change to the fork?

hey, catchy name, for some ms I thought of iOS... maybe it&#x27;s just me doing too much iOS development in the last months.

Can one of the 8 (so far) up-voters tell me whats interesting here?<p>The linked readme tells little.<p>-----<p>Now 25 pts with just as much explanation....<p>-----<p>As of 48 points, this (1) is the most relvant and informative explanation, but still has nothing to do directly with the linked OP.<p>(1) <a href="https://news.ycombinator.com/item?id=8669743" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8669743</a>

With the few forks and stances that everyone is taking now, I really hope that an amazing project like Node doesn&#x27;t get f<i></i>* up by becoming fragmented and multiple different &quot;versions&quot; appearing.