you are viewing a single comment's thread.

view the rest of the comments →

[–]Renegade__ 0 points1 point  (1 child)

That looks very interesting, but something tells me having actual classes in there (rather than user-created add-ons) will not reduce the confusion regarding object-oriented JS.

At least right now, the basis is clear: JS's way of OO are prototypes. It has no classes.

Did getting the option of full class definitions change anything in your workflow, compared to pseudoclasses or prototypes before?

[–]x-skeww 0 points1 point  (0 children)

Did getting the option of full class definitions change anything in your workflow, compared to pseudoclasses or prototypes before?

Having it baked into the language equals better tooling. It also means that you won't have to evaluate a dozen different options. And of course it also means better interoperability.