As far as I'm concerned you want to use a SPA when you have dynamic interlinked state. None of these sites have that. You give up so much simplicity going to SPA its kinda crazy and again I say that as a person who loves Svelte but I think is only necessary for occasional core pages.
But I constantly doubt myself, I must be missing something? Maybe its just easier for large orgs with dedicated frontend/backend devs but it really doesn't seem efficient.
I honestly think it's bad implementations of SPAs that give them a bad name. The web experience for Reddit so just terrible. Thank god (and the original devs) for old.reddit!
I think nowadays it's just easier to develop SPAs and make changes along the way. Frontend and backend teams can be separate and work more independently. Most of the issues mentioned here why people dislike SPAs (e.g. no back proper button) can be fixed.
The ability to press back on tutorials is incredibly useful. And the site seems unnecessarily slowed down by SPA. There's nothing here that needs a SPA besides logging in and gamifying that you completed a tutorial.
The ridiculous thing about SPAs is that any SPA website is either content better served without the SPA experience or is some ambitious application that happens to execute in the browser and doesn’t need the weight of common SPA frameworks.
The API documentation for one of our partners is a SPA that never should have been. There is no way to share a URL to a specific piece of the documentation because all navigation is handled in JS.
As far as I'm concerned you want to use a SPA when you have dynamic interlinked state. None of these sites have that. You give up so much simplicity going to SPA its kinda crazy and again I say that as a person who loves Svelte but I think is only necessary for occasional core pages.
But I constantly doubt myself, I must be missing something? Maybe its just easier for large orgs with dedicated frontend/backend devs but it really doesn't seem efficient.