


There were things like gnode, which allows you to use generators in node by interpreting your code during runtime (or turning on the Harmony flag for generators in node >= 0.11.x) Babel JavaScript Compilerīefore JavaScript-to-JavaScript transpilers became a (serious) thing, there were modules that would add specific bits of ES6 functionality to your apps. But we didn’t always have these tools and they weren’t born as mature as they are today.

In this post I wanted to briefly touch on the history of ES6 tooling and why I believe that today we’re in a much better place to adopt ES6 than where we were half a year ago.įor the most part, we have Browserify, Babel, and the spec being finalized to thank for. I’ve had an interest in ES6 for a long time, but we weren’t always prepared to write code in ES6. I wrote a few articles about React and ES6 these last few days, and today I wanted to add a bit more of context as to why I seem to be super into ES6 all of sudden.
