5 ms·
I've been trying to stay away from doing public facing web apps for a decade, so, from my point of view, hydration doesn't make any sense. Authorization is in
by beebeepka 4y ago
I've been trying to stay away from doing public facing web apps for a decade, so, from my point of view, hydration doesn't make any sense.
Authorization is in the browser, meaning I get to serve the login page "real fast".
That said, I get the reasons people do it, but frankly, it doesn't sit well with me. It's guaranteed that the whole process is unreasonably complicated as opposed to serving a few static files that can be cached and everything.
I'm theory, it could benefit people browsing without JS but I am not sure if things work out this way. Do next next require js on the client to display whatever was "rendered" on the ui server?
- jessaustin 4y agoAuthorization is in the browser... I'm probably missing some details, but this seems like a Bad Idea.
- jozzy-james 4y agorealistically speaking, if done correctly - SSR would allow the site to work without JS. Now, in practice, that comes down to what is required on the client side for interactivity - which is a case by case basis, and if your site doesn't require JS on the FE at all, why would you use it for the backend
- oblak 4y agoYeah, but at the same time, who the hell would use nuxt/next for the type of site that is perfectly usable without js.
- jozzy-james 4y agoi ask myself the same question, but apparently they're out there
- epolanski 4y agoYou can still cache ssr websites and render them only once.