web and framework stuff
Sure, it's undesirable to load massive JS bundles for basic functionality on websites, you'll find no disagreement there - I've been complaining about this for years too.
But arguing for all high-level framework-esque functionality to be handled by the browser and web specs...
Have you thought about what happens to the process of incremental technological improvement when the 'universal runtime' (ie. the browser) starts focusing on providing high-level abstractions instead of improving low-level mechanisms, and so the set of viable design strategies is essentially frozen in time?
web and framework stuff
It sometimes feels like some of the "just use native browser features instead of frameworks" people are not so much arguing against frameworks, as they are arguing for browsers to be the only blessed framework going forward...
web and framework stuff
To perhaps make it more explicit: aiming for performance and accessibility *does not* actually require eliminating diversity in technical approaches, and if you act as if it does, I'm going to be pretty suspicious of your intentions
