SPAs Were a Mistake
SPAs are a pattern that&#x27;s been applied too broadly IMO, but it&#x27;s going a bit far to call them a mistake. The aims of an SPA are pretty noble - the idea of essentially removing the network round trip when a user clicks on something is not a bad one. It means things are faster, they work if your connection is flaky, they can do things like offline support. Those are <i>good</i> features.<p>They might not be actual <i>requirements</i> for a blog or a brochure site but it&#x27;s not totally unreasonable for someone to want their website to work that way. The question is not whether or not an SPA is a good or a bad thing, but whether or not the cost (more code, more complexity, potentially a series of background requests after the initial page load) is worth paying in order to get the benefits.<p>When either an SPA or a multi-page site is done well most users can&#x27;t tell which sort of site they&#x27;re looking at. <i>That</i> should be the goal. Make stuff where the user forgets about the tech. Make a website that just works, that&#x27;s fast enough for users not to think &#x27;this is a bit slow&#x27;, and that&#x27;s coded in a way you can maintain and work on for a long time. If you get those things right then no one can reasonably criticise what you&#x27;ve made no matter how you&#x27;ve made it.