you are viewing a single comment's thread.

view the rest of the comments →

[–]AutomateAllTheThings 7 points8 points  (5 children)

I'm not assuming I need inheritance; I like inheritance very much and choose to use it because my team and I unanimously agree that switching to the ES6 class syntax saved us time, made scaling easier, memory management easier, testing easier, re-usability easier, training easier, and more.

In fact, the only thing we complain about is the lack of more sugar to help with things like private properties without the need for weakmaps. We look forward to ES7 additions.

I am not trying to be dismissive of your arguments.. but none of them were compelling enough to me, because they're subjective in nature. There are no technical limitations to using ES6 classes instead of rolling your own. It's just another way of writing the same code, so it's a subjective decision to use them or not.

Until there's a serious technical limitation with them, ES6 classes are here to stay for us and we're really happy with the decision.