IO.js – Evented I/O for V8 javascript
github.com
IO.js – Evented I/O for V8 javascript
1–10 of 48 posts
Re: IO.js – Evented I/O for V8 javascript
#2With what purpose? What's the significance of this? node is also node with many of the key contributors.
Re: IO.js – Evented I/O for V8 javascript
#340 minutes, 8 points, got to the front page, and... why? Is there a story behind this fork?
Re: IO.js – Evented I/O for V8 javascript
#4Can 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.
Re: IO.js – Evented I/O for V8 javascript
#5Can one of the 8 (so far) up-voters tell me whats interesting here?
The linked readme tells little.
-----
Now 25 pts with just as much explanation....
-----
As of 48 points, this (1) is the most relvant and informative explanation, but still has nothing to do directly with the linked OP.
Re: IO.js – Evented I/O for V8 javascript
#6With the few forks and stances that everyone is taking now, I really hope that an amazing project like Node doesn't get f* up by becoming fragmented and multiple different "versions" appearing.
Re: IO.js – Evented I/O for V8 javascript
#7Can 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.
The same reason anyone forks: some core developers are not happy with the way development is headed.
The reasons are myriad, both technically and politically, and you probably won't understand them unless you engage. If they weren't, we wouldn't be seeing something as drastic as a fork.
Re: IO.js – Evented I/O for V8 javascript
#8With the few forks and stances that everyone is taking now, I really hope that an amazing project like Node doesn't get f * up by becoming fragmented and multiple different "versions" appearing.
sigh time to start looking into Go
Re: IO.js – Evented I/O for V8 javascript
#9Can one of the 8 (so far) up-voters tell me whats interesting here? The linked readme tells little. ----- Now 25 pts with just as much explanation.... ----- As of 48 points, this (1) is the most relvant and informative explanation, but still has nothing to do directly with the linked OP. (1) https://news.ycombinator.com/item?id=8669743
Compare with https://github.com/joyent/node, similar readme and commit numbers. Looks like a node.js fork. (EDIT: maybe you already understood that, I thought it might have been a different thing from node.js altogether until I saw the repositories shared a README/history)
Re: IO.js – Evented I/O for V8 javascript
#10Can 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.
Joyent is accused of:
1. Fixating on platform stability over project evolution
2. Ignoring the community on project direction
3. Preserving public image over project committers
4. Being a total square
NOTE: I am against the fork.