EcmaScript 5 versus 6
Still to this day I continue to hear professionals complain about ES6, and watch followers hold the same opinion because of a close-minded programmer. Even being new to JS, I’m not new to programming, and this is the first time I’ve seen people completely retaliate against their own language. In this article I plan to cover what I’ve experienced, and why I think people with this mindset are doomed to fail.
To ease the minds of many, I would like to point out with ES6, ES5 syntax is not phased out, so you can continue how you would normally, and at least use ES6 for some of the sugar. Like the founders of Elm always say, “Write just a little bit of your project with it, and then a little more. You do not need to refactor the entire project, just add a little bit at a time”. This can be said for ES6 just as well, except with ES6, you can mix ES5 in it. If the sight of task-runners, and bundlers is what is turning you away, simply look around GitHub for boilerplates. You can clone, run, and done. Learn it when you absolutely need to, or have the time.
To make a long story short, I highly recommend learning ES6, as well as always learning about how your language evolves when the official changes are released. With ES 2015, the syntax makes for some great code, allowing for easily written functional programming, and easily readable code. The class ability allowing for the easily written ability to create entire closures, with the ability to easily expose any method to the public with a single keyword , as well as many other patterns (like ‘let’ singletons). Then you have the built-in Promises and Generators that help create amazing asynchronous control flows when working in redux, or Node.js. There’s just so much possibility, and I’ve only skimmed the surface.
To learn more about ES6, I highly suggest checking out this great Article over at Medium.