If you were working in C/Java/etc I'm sure your first reaction to the same problem wouldn't be "C is broken because I can't debug a compiled executable easily!".
It's a long list: https://github.com/jashkenas/coffeescript/wiki/list-of-langu...
Also, ultimately, there will be code that you can't maintain because you don't understand it. That might be because it's written in a language you don't know, but it might also be because it's written in a style you don't understand, or with a framework you've never used, or because it's about a topic that you haven't spent time with. That's OK. You don't need to be able to do everything.
Also - thanks for taking the time to make a thoughtful reply instead of just suggesting I'm a complete ignoramus and downblasting my response because we have a marginal disagreement about the Open Web Platform - made my day!
Right now, if you are a frontend "web developer", you can pretty much assert what you know from the title alone. The title implies the toolset.
In ~5 years? It means.. what, HTML/CSS, and whatever language you prefer? Rust? C++? Python? JavaScript? An endless array of frameworks in a sea of different languages?
I mean, it's no different than most other development in that regard.. but the web certainly will go through a change when this day comes.
> You keep citing examples of cleaning up after other people for a job. Why don't you have their source code?