As for me, I was taking UX into foremost consideration, too. Spa as way better UX than non-spa — unless for edge cases.
July 27th, 2019
Your main concern should be user needs—not your own.
When I talk about over-engineering, I’m speaking from the perspective of end users, not developers.
Before considering your ease of use, and maintainability, consider users first.
Yes. I’m not sure what the point of contention is here, though. In your prev tweets you’ve already said that PE is ok. Are you differentiating PE spas from spas generated by e.g. Gatsby etc.?
There’s a point with server-rendered React and Vue (to a point) where the entire static output of HTML is fully hydrated. This is what is incredibly expensive and if something goes wrong (it will), the page will be left blank. All of that for no-reloads seems risky to me.
Even if true (hydration is non-optional), it still seems your worry is not of UX/perf, but rather that since JS is way more complex than HTML we should abandon it.