The irony is that the introduction of XHR was intended to avoid page reloads which were seen as a major source of inefficiency. Not all websites need to be dyn

The irony is that the introduction of XHR was intended to avoid page reloads which were seen as a major source of inefficiency. Not all websites need to be dynamic, though. And I'm with you in spirit. I just think that throwing out JavaScript entirely throws out the baby with the bath-water for a lot of websites. In theory, you can use XHR and client-side rendering to make things smaller, not bloatier. Fetch the HTML once with first content, then fetch only content updates at the user's request without reloading the page. This can result in better cache efficiency and improved render times. But a lot of people might object on principle to the idea of using XHR requests and dynamic behaviour in something called "small web."