3 ms·
From my limited understanding of the situation as a casual observer, I'd say the optimal (or at least simplest) outcome here would be to do an egcs/gcc-style sw
by vezzy-fnord 12y ago
From my limited understanding of the situation as a casual observer, I'd say the optimal (or at least simplest) outcome here would be to do an egcs/gcc-style switch where io.js is officially christened as the next Node.js, and the incumbent Node.js deprecated.
That said, I'm not sure if Joyent will be receptive to such a move.
- deleted 12y ago[deleted]
- jballanc 12y agoMy thoughts exactly. I think anyone not familiar with the history of GCC/EGCS would do well to read up a bit...the current node.js/io.js situation almost an exact parallel. I also hope that Joyent takes note that EGCS was probably one of the best things to happen to GCC, and that the shift in governance model is likely one of the reasons for GCC's current success.
- cpeterso 12y agoThis page has a detailed timeline and emails from the GCC/EGCS schism: http://www.softpanorama.org/People/Stallman/history_of_gcc_development.shtml http://www.softpanorama.org/People/Stallman/history_of_gcc_d...