3 ms·
Understanding Server Side Rendering
- sattoshi 7y agoI’m unsure how much of a response this post warrants, so I’ll keep it brief. Almost each of the points listed is wrong. It’s as if someone read a post about SSR for the first time and wanted to retell it. > Better SEO This point rests on googlebot’s inability to execute js. This premise is false. > Great for static websites You wouldn’t use SSR for static websites. You would serve generated static files. > More server requests The author has never heard of rehydration. SSR doesn’t mean you can’t have an SPA right after. > Slower page rendering He says that it “paints” (renders) the page faster. That previous claim is almost universally correct. > Less interactivity Once again, hydrate your renderer content. Dev.to did a great job at appealing to people who just got into programming, however it has grown into a strangely polite and courteous Circlejerk. I was one of the earlier members of the site when it just launched (and got stickers for it), but the value of going there is very limited.