Hacker News new | ask | show | jobs
by paulryanrogers 351 days ago
If by 'nicer' one wants to avoid the flash of blank between clicks, then I don't see how you'd avoid recreating an SPA
5 comments

This doesn't happen for me when clicking around sites like HN or my blog, both are server side rendered and I'm on a pretty flakey connection right now. Browsers solved this a long time ago with how they deal with page changes.
your connection is not flaky enough. for me the average page load on HN is a full second. i just had one page take 1.8 seconds...

(edit) submitting this comment took 1.5 seconds.

I read the server-side-rendered forums of DLang, and everything happens so fast, in around 200 ms, that I don't feel I am losing anything by the forums not being an SPA.
The View Transitions API (https://developer.mozilla.org/en-US/docs/Web/API/View_Transi...) is intended to let you control transitions between clicks.
I mean, is this really a legitimate problem? Full page reloads don't bother me very much at all, and they actually come with a lot of niceties. Like URLs and the back button working normally.
For me personally, not usually. But having worked on a few different companies with embeddable widgets, yes it is. The page-based (SSG) routing is not an option there. And even in CRUDs the product folks want WYSIWYG and smooth uploads of assets. With more and more bling it's just inevitable that one will need a JS framework eventually.
Browsers haven’t left a flash of blank for decades.