Good stuff Jordan. I agree with all your concerns. The question I had to resolve for myself was: How do I present ES6 classes to my team? Forbidding their use feels too strong. Embracing (for the reasons outlined in the article), but explaining the risks feels like a fair compromise.

What would you do if you saw an ES6 class in a code review? Saying “You must refactor because there’s a better alternative” feels too strong to me.