There were bad design decisions made with JavaScript (for example; the handling of <code>this</code> ); we have had “JavaScript: The Good Parts”, for a reason.
But ES6 improves upon the above said bad parts; introducing keywords like <code>let</code>, <code>const</code>; and better handling of <code>this</code> through fat arrow functions. 
My question is this — With ES6, would you still say that there are any bad parts left… (I am not talking about the lack of features) in JavaScript; ones that are still to be addressed?
Some would argue that <code>class</code> is the new bad part, with ES6; but that is debatable.
Curious to know the opinions of the JavaScript pros in here?


There were bad design decisions made with JavaScript (for example; the handling of `this` ); we have had “JavaScript: The Good Parts”, for a reason.

But ES6 improves upon the above said bad parts; introducing keywords like `let`, `const`; and better handling of `this` through fat arrow functions. 

My question is this — With ES6, would you still say that there are any bad parts left… (I am not talking about the lack of features) in JavaScript; ones that are still to be addressed?

Some would argue that `class` is the new bad part, with ES6; but that is debatable.

Curious to know the opinions of the JavaScript pros in here?

Does ES6 eliminate all of the bad parts of JavaScript?

Product

Explore

Company

Blogs

Partner with us

Support

Comparisons

Comparisons