I think the cheatsheet does a great job of summarizing what makes me uncomfortable with es6 classes:<p>&gt;&quot;...the syntax for creating classes in ES6 obscures how implementation and prototypes work under the hood...&quot;<p>Yes, it&#x27;s great for if you&#x27;re uncomfortable with prototypal inheritance and the &quot;javascript way of doing things&quot; (I&#x27;ll maybe summarize that as composition over inheritance, mixins, knowing how to use call&#x2F;apply etc.), but at the end of the day I&#x27;m worried it might be a crutch. Specifically, it might create the situation where a javascript noob might use es6 classes and never bother to learn how the prototypal chain works or all the myriad options available for mocking classes and OO behavior. That being said, maybe that&#x27;s a shitty argument. When you have more tools in the toolbox there&#x27;s always the option for someone picking the wrong tool. Does that mean you take the tool out? Or leave it because it is really useful when you know when to use it correctly. I imagine the latter.