Thanks for the thoughtful response. Regarding your “shoe on the other foot” example, the important difference is that ES6 class is actually here. It shipped as part of the ES6 standard. Whether it should have is water under the bridge.

Thus the real question is whether we should allow people to use this standardized, yet admittedly less than ideal tool. I believe code reviews are the solution to avoiding ES6 class risks, misuse and overuse, rather than a blanket “ES6 classes are bad and should never be used” mandate.