4 ms·

> For example, "class" is just syntactical sugar This was true up until we got #private vars in JavaScript. Now classes have their own very special rules very

• danShumway 7y ago
  I'm still a little upset about that. Privates should have been held back until we could figure out how to build them in a more generic, consistent way. Their implementation is very out-of-character with the ideals of the extensible web. They feel like a hack designed to solve a very specific high-level problem, rather than a low-level tool that can be adapted in flexible ways. The whole thing honestly felt bad. There was a lot of debate around the standard, some of it pretty toxic. Things that were problematic got pushed through because nobody could think of a better solution and they didn't want to delay. The debate kind of degraded from there and people started accusing the champions of not caring. It's... I dunno. The whole thing felt like a bad picture of the JS community, and I wish the standard had been temporarily binned so we could get rid of the worst actors and then think of something else in an environment with fewer emotions. There was a never a chance for something good to come out of an environment that toxic. And there was no reason that privates needed to be standardized right now. It's OK to take things slowly.