I’m quite unfamiliar with OOP in JavaScript, so I’d appreciate if someone could chime in with how this differs from ES5: is this just syntactic sugar, or is there a semantic change as well?
> JavaScript classes, introduced in ECMAScript 2015, are primarily syntactical sugar over JavaScript's existing prototype-based inheritance. The class syntax does not introduce a new object-oriented inheritance model to JavaScript.
[1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
I found the ES6 classes to be very helpful in conceptualizing stuff. When I started playing with them I’ve built myself a demo https://codepen.io/ronilan/pen/PObzew as a clone of same done previously in Ruby. Then I found classes to be very useful for bigger “vanilla” projects (https://github.com/ronilan/BlockLike)
I’d call them “syntactical vitamins”.
I would argue that, more often than not, it is, and it becomes less healthy the more of it you have.
Javascript, for all its faults, is syntactically a simple language and it should have been kept that way.
My favourite subtle distinction is that methods are not constructors—this is true of object shorthand as well.
You were taught that these two were equivalent?
var x = { foo() {} };
var x = { foo: function() {} };
new x.foo
(To demonstrate this same point in ES6 classes, `new (new class { foo() {} }).foo` will fail.)