“…your post makes the false assumption that classes will be the one feature to rule them all.”
I don’t expect global agreement at all. But I do expect each project to make a decision on how they want to handle objects, and to do so consistently within a given project. Sure, make exceptions as necessary, but every developer on a given team using a different style is a problem that ES6 classes can help solve. They offer a low barrier to entry for consistency, and you’re still free to utilize an alternative strategy in the cases when it’s truly necessary.
I’m not suggesting everyone standardize on ES6 classes. But I am suggesting they’re potentially helpful for certain teams.