If, instead, you wanted to say "can everyone please use the things I like?", I'm sorry but that's not how it works. You don't get to tell people what they should do just because you're "tired".
The idea that complexity arose out of nowhere and not because the web is doing things we couldn't have even imagined 10 years ago has always been wild to me.
My main complaint is that by and large, the people who are applying these technologies heavy-handedly are doing so because they either think it’s needed, or because they don’t understand that simpler tools exist that could solve their problem.
I guess I just don't really see this being a problem outside of social media.
And I think another aspect that gets lost is that 20 years, your options were slim. Which means picking the right tool for the job was easier (because even if it wasn't the right tool, chances are it was as close as you were gonna get).
Things are different right now. Even something as ubiquitous as authentication is vastly different than it was back then. There's way more at play when picking tools nowadays, so it doesn't surprise me when people get it wrong.
The other issue is, many websites are basically apps. The HTML is a byproduct, it isn't the main event. The template based systems are fine if you have mostly plain HTML with some interactivity sprinkled in, but for people who are building complex web apps, there is typically a tiny bit of HTML and a lot of logic.
The old template based systems fall to pieces for really complicated sites.
In regards to language, if you are going to pick a JITed or interpreted language, may as well pick one that has had a lot of effort put into making it fast, and the JS runtimes are really optimized by now. Java is faster, but Typescript is a much better language (and more type safe!) than Java.