SPAs are the best we can do for... applications. Online spreadsheet? SPA. Document editor? SPA. Image editor? SPA. Visual programming environment? SPA. IDE? SPA. Facebook makes sense as an SPA too - it's basically a rich widget "dashboard" app with some content creation applications inside of it. Building applications for the web is still not the greatest experience because you're fundamentally building an application over hacks built to expand an abstraction built for hypertext content (the DOM). But, honestly modern JavaScript frameworks, TypeScript, and transpiled environments like Elm all do an admirable job working with what they have.
On the flip side, SPAs are terrible for hypertext content, because existing web technology was literally built for that. Why should a blog be an application? The content creation side, sure, maybe, but viewing a blog? That's literally what HTML was made for. A table of contents full of links like the HN or Reddit homepage? That's pretty much hypertext 101.
On the flip side, SPAs are terrible for hypertext content, because existing web technology was literally built for that. Why should a blog be an application? The content creation side, sure, maybe, but viewing a blog? That's literally what HTML was made for. A table of contents full of links like the HN or Reddit homepage? That's pretty much hypertext 101.