I've been aghast at the broad adoption of thick client JS frameworks on the open web and a growing open hostility towards progressive enhancement, as if it's somehow not possible to build a single page app without totally breaking everything that makes the web a great platform.
There is a reasonable argument to be made that the vast majority of websites should not be using one of these, as the majority of these frameworks are incompatible with progressive enhancement and progressive enhancement is still the best way to build most sites. I firmly believe vanilla JS should be everyone's default. There are exceptions, but those exceptions are very narrowly tailored. I think this article which outlines those exceptions should be required reading for every web developer.
It seems like a lot of people these days don't realize you can build single page apps using progressive enhancement. And when you do, they perform better and are more fault tolerant while avoiding an unnecessary hard JS dependency. This whole stereotype you hear from people about single page apps being the future and progressive enhancement being the past is the most annoying false dichotomy ever. You can do both so long as you consider choices other than big, largely badly designed frameworks. It seems like most people who use Angular just want to make websites that don't reload the page when you click links. Maybe consider using a client-side router library instead of a giant monoframework. Way less code that has to be dumped on the user.
I'm not saying it isn't possible to use the big monoframeworks responsibly. The article above outlines good use cases for them. If you're building a client-only Electron app for instance, then go nuts with React or whatever if you like it. But seeing people design regular websites on the open web that are mostly just text, forms, and images using things like Angular and React is the biggest, most depressingly popular cargo cult antipattern we've seen since the days of Flash sites.