3 ms·
As far as this repo is a fork of IO.js i'm not sure this is going to work out as a "merge". I think Joyent should consider their defeat and recover the bridges
by drinchev 11y ago
As far as this repo is a fork of IO.js i'm not sure this is going to work out as a "merge". I think Joyent should consider their defeat and recover the bridges they've burned.
On the other hand, it would be amazing if I could do brew install node and get iojs on my Mac.
- m3Lith 11y agoAs they've said, the "merge" would most likely happen as a forked io.js repo with cherry-picked commits from node's repo.
- elisee 11y agoThe (draft) convergence plan details how the merger is likely to be handled, including on the technical side: https://github.com/jasnell/dev-policy/blob/master/convergence.md#converging-the-projects https://github.com/jasnell/dev-policy/blob/master/convergenc... EDIT: Hmm, didn't see this one linked from the OP: https://github.com/jasnell/dev-policy https://github.com/jasnell/dev-policy. Not sure why there are two documents with similar purpose.
- drinchev 11y agoI didn't see that too. I wish both teams seamless convergence! It's a great news for the community. I hope business guys will not modify this in a non-sense way.
- gtf21 11y agoJust use `brew install nvm` and `nvm install iojs`
- utunga 11y agowoosh