


The same question raised for ES5 and CoffeeScript too.

One common question about using another language is compatibility. Is It Safe to Use ES6 Now?ĮS6, also known as ECMAScript 6, or ES2015, is the latest JavaScript specification released in 2015. Also I will refer the “pure” JavaScript as ES5 because ES5 was the specification before ES6 was released. In this post I will show you some reasons why you should switch to ES6 (and more) if you have not done so. I have some experience of converting legacy JavaScript code to ES6 style and it did save us significant amount of time solving the bugs caused by quirky JavaScript. Since 2015, ES6 (ECMAScript 6) has been out for years and it has been accepted by most developers and has been proven safe and effective. It was not because of I didn’t know about “pure” JavaScript, but because I don’t feel like to work for guys who don’t know about ES6, or at least, don’t want to use ES6. Interviewer: Well, would you please write in plain JavaScript?Įventually I didn’t show him the “pure” JavaScript code. Interviewer: I’m sorry but would you please write in JavaScript? Me: (Writing JavaScript code on the whiteboard…) Interviewer: Can you write some code for this function? A couple of month ago I attended an interview for a front end developer position and had an interesting experience.
