But whatever tools you used to use for the "vast majority" of web applications probably still exist. You are under no obligation to use the newer tools. Other p

But whatever tools you used to use for the "vast majority" of web applications probably still exist. You are under no obligation to use the newer tools. Other people are developing new tools for their different needs and different applications, but this doesn't place a demand on you to follow suit. For example, there's tons of libraries provided via CDN so you can link them in script tags. That's as far back as I can think in terms of JS tooling. Bower still exists. So do grunt and gulp. jQuery is still releasing new versions, so is angular 1. I assume backbone and knockout still exist. If javascript fatigue was an epidemic, then there would be a huge swath of developers who just want to use the current, existing tools. That would surely provide a solid maintenance base for these existing tools so you can continue to use them for a very long time. Javascript fatigue seems like a self-correcting problem.