4 ms·
You might remember the io.js fork of Node.js back in 2014. Node was stagnating, a bunch of people forked it into io.js, which eventually got merged back into No
by johnfn 4mo ago
You might remember the io.js fork of Node.js back in 2014. Node was stagnating, a bunch of people forked it into io.js, which eventually got merged back into Node and got it back on track. Or, going further back, CoffeeScript, a "fork" of JS that had its best ideas adopted back into ES5.
A small scrappy team can prove out a good idea because failure is not a catastrophic risk to them. In short, forks are part of a healthy ecosystem.
- hootz 4mo agoIt is still happening, a lot of things are still being adopted by Node after being available on other runtimes. They aren't forks, but they still provide pressure towards progress.
- psygn89 4mo agoBeautifully stated reminder :)
- colinmcd 4mo agoI almost called it "oi" but I'm not sure anyone would have gotten the joke :P
- NamlchakKhandro 4mo agoye wot mate?
- throw1234567891 3mo agoyour sure?
- llbbdd 4mo agoI had a lot of very good times with CoffeeScript but I'll never forgive it for having implicit returns. So many subtle event-bubbling bugs caused by that.