I feel the same, I agree that the web has gone downhill with all the endless JavaScript wasting all the available CPU cycles. (With all the rest CPU cycles being wasted by the swap-in/out because of the memory bloat of web browsers, again.) This is why these days I ALWAYS enable Low Power Mode in any browser or system that provides such a functionality; macOS has finally added this a few years ago — better late than never.
But I feel like ALL browser vendors are not doing enough to combat this bloat. There have to be resource limits, warning messages/icons, and stop-gap measures to avoid pointless JavaScript wasting our electricity; but NONE of the browsers do this to an extent I'd wish they'd do; in fact, Chrome has actually been ahead of Firefox and Safari in reigning these sites, probably because it has to run in production on 4GB ChromeOS machines costing $99, whereas all the Firefox and Safari devs are probably using 48GB machines costing $2399 as their benchmarks. So, the reality, is that, ironically, Chrome is again the leader even in this area. Because Chrome on a $99 4GB ChromeOS machine feels snappier than Firefox on a $999 MacBook, given enough open tabs.
Your point about feature bloat sounds good in principle, but is not practical in reality. In reality, if things don't work in Safari, you're simply asked to install an app from the App Store. Or if you have to configure a keyboard on a Mac, you have to use a Windows machine with the native keyboard configuration tool, instead of VIA in Chrome WebHID or WebUSB. Why in your opinion are these alternatives not worse than having these sorts of things as web standards as written by Chrome?
But I feel like ALL browser vendors are not doing enough to combat this bloat. There have to be resource limits, warning messages/icons, and stop-gap measures to avoid pointless JavaScript wasting our electricity; but NONE of the browsers do this to an extent I'd wish they'd do; in fact, Chrome has actually been ahead of Firefox and Safari in reigning these sites, probably because it has to run in production on 4GB ChromeOS machines costing $99, whereas all the Firefox and Safari devs are probably using 48GB machines costing $2399 as their benchmarks. So, the reality, is that, ironically, Chrome is again the leader even in this area. Because Chrome on a $99 4GB ChromeOS machine feels snappier than Firefox on a $999 MacBook, given enough open tabs.
Your point about feature bloat sounds good in principle, but is not practical in reality. In reality, if things don't work in Safari, you're simply asked to install an app from the App Store. Or if you have to configure a keyboard on a Mac, you have to use a Windows machine with the native keyboard configuration tool, instead of VIA in Chrome WebHID or WebUSB. Why in your opinion are these alternatives not worse than having these sorts of things as web standards as written by Chrome?