IO.js, a Node fork
iojs.org
IO.js, a Node fork
1–10 of 30 posts
Re: IO.js, a Node fork
#2Great, a node.js fork.
Re: IO.js, a Node fork
#3But why?
Re: IO.js, a Node fork
#4Great, a node.js fork.
[deleted]
Re: IO.js, a Node fork
#5Questionable way to start: "This organization has no public members. You must be a member to see who's a part of this organization."
Re: IO.js, a Node fork
#6Not looking for dirt or anything, but why the fork? What makes this different from Node?
(Only clue so far is the "open governance model"; is that in contrast to Joyent maintaining Node?)
EDIT: Based on their CONTRIBUTING.md page[1], it looks like this is intended to be a more "community-driven" version of Node. A strike against is that SEVERAL (if not most) links in README.md and CONTRIBUTING.md still reference the joyent/node GitHub project.
[1]: https://github.com/iojs/io.js/blob/v0.12/CONTRIBUTING.md
Re: IO.js, a Node fork
#7Any background on who's doing this or what the motivation is?
The linked site doesn't have much content besides a link to the GitHub repo.
EDIT: Even though it's not explicitly listed in the README or contributor list, the commit history does show a bit of detail: https://github.com/iojs/io.js/commits/v0.12
Re: IO.js, a Node fork
#8Cool fork, bro.
Re: IO.js, a Node fork
#9[deleted]
Re: IO.js, a Node fork
#10Any background on who's doing this or what the motivation is? The linked site doesn't have much content besides a link to the GitHub repo. EDIT: Even though it's not explicitly listed in the README or contributor list, the commit history does show a bit of detail: https://github.com/iojs/io.js/commits/v0.12
Wired has a pretty good high level overview: