A lot of its ideas got folded into subsequent versions of ECMAscript, so in a way everyone uses it now. But for the actual "language" and runtime, it seemed fro

A lot of its ideas got folded into subsequent versions of ECMAscript, so in a way everyone uses it now. But for the actual "language" and runtime, it seemed from the start to have a built in expiry date, so I tried to avoid it as much as possible, mostly successfully. Ultimately, if you want tomorrow's language features today, Babel feels like a better approach. You can choose your level of "buy-in" and then one day, certain things "just work" because they've been built into the runtime, and your code stays the same. Or at least, that's the hope. Making a new sub-language to get a handful of cool features/syntax involves a lot of pain for not enough gain, IMO.