4 ms·
Why would you want server side rendering? As a user it's painful if you have to wait after each click
by tffgg 6y ago
Why would you want server side rendering?
As a user it's painful if you have to wait after each click
- slt2021 6y agois it painful for you to click on HN? I find this website rapid fast. Also because you dont have long running JS processes the RAM consumption is low and everything feels very quick, unlike most SPA garbage
- tffgg 6y agoYeah, I kinda wish clicks would respond instantly
- goostavos 6y agoYour comment made me legit chuckle. Rather than "waiting" after each click, we get an instant 'page load', half of which can't be interacted with (looking at you, Amazon.com), and then a sea of loading spinners -- all under the guise of 'not waiting'. I'm not sure which of those I prefer, tbh. I'm partial to good ol' fashion SSR sites these days, as I do most of my casual couch browsing on an old chromebook running Ubuntu. The number of heavy-weight SPAs that I just can't run on the hardware anymore seemingly climbs by the day. :(
- tazjin 6y agoThere is - by definition - more overhead in client-side rendering. Think of it this way: The server needs to first serialise data, the client needs to deserialise it, then it needs to construct the DOM to update. The server can just do the first step and things like Hotwire can add the dynamic bits you need - all overhead and extra processing is now gone. I can list a lot of websites that don't render client-side that are fast, but very few that do which are.