But the problem of new features hasn’t gone away. It’s only moved.
Now instead of wondering how I can work with generators, I’m looking for opportunity to work with async functions and other ES2017 (and beyond) features.
Sure, we can install new versions of Node.js on our server and run new code in the back-end. But even that can be dangerous.
“That’s great! I’ll just install the latest, unstable Node.js release, update my Babel.js version and plugins, and download an experimental browser versions that might support this syntax if I use command-line flags when starting it!”
If you’re like me and millions of other developers, this isn’t even a remote possibility. It’s just not going to happen.
Because you have existing projects that need tried-and-true, stable, well-tested and supported versions of all these things. And the risk of installing new, unstable and experimental versions of Node, Babel or any other runtime, and having it break your actual work is far too great.
On May 2nd, I’ll be presenting a live WatchMeCode session all about this problem and solution.