5 ms·
The previous fork was successful because a lot of the developers went with the fork and it was fulfilling an unserviced need in the community for a node built o
by kybernetikos 9y ago
The previous fork was successful because a lot of the developers went with the fork and it was fulfilling an unserviced need in the community for a node built on newer versions of v8. Does anyone know if this fork has much of a chance of survival?
- LoSboccacc 9y agodidn't follow the node development closely, what was this fork?
- photonios 9y agoIt was called io.js.
- zeronight 9y agoAnd this one is pronounced the same way? That won't be confusing in conversation.
- pfranz 9y agoio.js https://en.wikipedia.org/wiki/Node.js#History https://en.wikipedia.org/wiki/Node.js#History
- ZenoArrow 9y agoThe previous fork was io.js, it's contributions have now been brought back under the Node.js umbrella. This new fork is almost a non-story by comparison, if it gets even a minor level of traction amongst developers I'll be surprised. Even the repo creator has half-arsed the readme.
- naibafo 9y agoio.js forked 2014, planning to keep io.js up-to-date with the V8 engine. Node.js foundation was later founded and later in 2015 io.js and node.js merged into Node 4.0.
- spartanatreyu 9y agoThis fork adds nothing, it's just a "politics" thing, I doubt it will survive past a few weeks
- smsm42 9y agoI'd be surprised if it survives into 2018 as anything more than "we copy commits from upstream and consider ourselves a different project".