I think we'll ask the same question about Typescript in the future; I've integrated into a UI project I work with other people, to make one of our devs happy, but I won't use it myself. A few years ago I remember having one colleague who wanted to write in CoffeeScript but at that time we didn't know how to interoperate with JS, I believe? Or our tooling or knowledge wasn't the best, so we decided not to let him write CoffeeScript; From time to time I hear from that team and the project is still alive - luckily they don't have to support CoffeeScript.
I think you should use whatever makes you happy, for your own projects, but in a team, have in mind others and the future.
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.