Yeah as best I can tell, Coffeescript was a thing because Ruby was very popular at the time, and some Ruby devs had to write JS but they wanted to write Ruby.
I also have fond memories of painstakingly converting hundreds of coffeescript files back to JS. There's something to be said for using the native language.
While I don't want to live in a super urban place like SF, I will always live near a downtown. The draw for me is that I hate depending on cars, so I want everything (mail/barber/grocery/work/restaurants/etc) within walking distance.
The lifestyle advantage to walking around as your primary source of commute is so significant that I couldn't imagine ever going back.
I'm not well versed in this area, but from my perspective, I see this as the fundamental problem:
Every action my brain takes is made of two components: (1) the desired outcome of the thought, and (2) the computation required to achieve that outcome. No matter how well computers can solve for 2, I have no idea how they'd manage solving for 1. This is because in order to think at all, I have to have a desire to think that thought, and that is a function of me being an organism that wants to live, eat, sleep, etc.
So for me, I just wonder how we're going to replicate volition itself. That's a vastly different, and vastly more complicated, problem.
I agree that the class keyword is far more readable. I never find myself using them in the "classical" sense, though I could see how it would be tempting for someone coming from, say, Java.
Is scoping an issue for you? Just use arrow functions!
Is callback nesting an issue for you? Just use `async/await`!
I love it so much.