The current state of SPAs is just a symptom of an overall illness the web is suffering from. SPAs just happen to introduce some annoyances that lazy and inexper

The current state of SPAs is just a symptom of an overall illness the web is suffering from. SPAs just happen to introduce some annoyances that lazy and inexperienced programmers don't avoid, often defeating the point of SPAs. The average SPA is not only written to experience zero latency but are poorly written from an efficiency perspective. They are often doing tons of procedures under the hood in order to support generalized programming when in actuality they could get by with a lot less framework code (Svelte in part demonstrates this in a positive way). Programmers waste so much time figuring put frameworks that they shirk proper exception handling, handing off complex tasks to the server, or giving the user cues as to what to expect. Most SPAs don't even need to be SPAs. If all the meaningful state belongs on a server then the app is better off being a traditional web site with progressive JavaScript enhancement. Not only does that free frontend code to be more UI centric but it also means JavaScript wouldn't be required. It amazes me how many blog sites don't work at all with JS turned off. That shouldn't be any more acceptable than it would have been to implement a blog entirely in Flash back in 2005.