3 ms·

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

• benatkin 12y ago
  There doesn't appear to be much of one, yet. The latest commit by indutny was just a commit to node that the owner of the iojs GitHub organization pushed to GitHub. There are no public members of the iojs organization. Even the name of the repo, "evented I/O for v8 javascript" is the same. All that's been introduced here is a new name, io.js.
  • denisw 12y ago
    Looking at the v0.12 branches of both iojs/iojs and joyent/node, it doesn't seem to me that idutny's latest commit (updating OpenSSL to 1.0.1j) was a commit to Node proper. I also can't find that commit in any other branch of Node, or on idutny's personal copy of Node (idutny/node). In fact, the history of Node and IO.js seem to completely diverge after Nov 21, with no overlap between the commits or contributors. To me, this seems to clearly indicate that the committors in these last IO.js commits are also the people behind that effort. Am I missing something?
  • cwmma 12y ago
    from the issues that have been opened [1] and closed [2] it looks like indutny, jonathanong, and rvagg are involved, aka all people involved with node forward 1. https://github.com/iojs/io.js/issues/5 https://github.com/iojs/io.js/issues/5 2. https://github.com/iojs/io.js/issues/7 https://github.com/iojs/io.js/issues/7
    • benatkin 12y ago
      Yes this appears to be the main thing at play right now. A small number of serious node hackers are contributing to io.js. This could be big, but it's too early for me to tell.