“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. Why? 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.
This is unfortunate, though. You've read so many blog posts and have seen such great syntax in Es6 and in what's coming down the line with ES7 and beyond:
- rest / spread params
- async / await
- updates to the class syntax
- native proxies
- … and so much more
What, then, are you supposed to do about this problem?
It's a simple solution to what can be a very complex problem, and it's all handed to you in a done-for-you manner, with the ES7 and Beyond code repository on github!
Also check out the live Q&A session that followed the presentation from this recording.