9 ms·
> because who wants to reload the page multiple times happily, please, yes. The browser caches pretty much everything but the HTML, so the payload is minimal.
by virtualwhys 7y ago
> because who wants to reload the page multiple times
happily, please, yes.
The browser caches pretty much everything but the HTML, so the payload is minimal. A fast SSR site is a dream compared to the myriad poorly implemented SPAs out there.
It's ridiculous going to, for example, an airline site; trying to book a flight and discovering that the damn reservation process is borked due to an uncaught exception in the latest update to the SPA (in which case the house of cards collapses, fun).
With an SSR the JS footprint is much smaller, which can lead to more stable/reliable apps.
I find the modern web to be a complete mess, but the loading spinners are nice, provided that the loading actually finishes (if it doesn't, look in the console and you'll likely find your answer in red).
- movedx 7y ago>> because who wants to reload the page multiple times > happily, please, yes. A yes please from me, too. I like knowing, for a fact, that the input I gave your website made it to your server, your server processed it, and then I got back a response. What I don't like is providing some data in a form, submitting it, being told, "Got it, buddy!", moving to another page on the site and then getting an error saying, "Acccctually something fell over. Sorry guy. Try again?" Give me that slower but guaranteed feedback.