3 ms·
wow. this is very true and I never thought it that way before. I'm an old school ruby on rails web app dev and I never liked the one main div and then DOM manip
by andrewfromx 2y ago
wow. this is very true and I never thought it that way before. I'm an old school ruby on rails web app dev and I never liked the one main div and then DOM manipulation on the same page for every click. Some react devs literally don't even know that HTML can be rendered server side.
- hermanradtke 2y ago> Some react devs literally don't even know that HTML can be rendered server side. Sadly, many do. Only later do they realize it is orders of magnitude slower than rendering a template and more cpu intensive. Combine that with the fact that node.js prefers to have an IO heavy workload, but instead we get a cpu heavy one. React is fine, but SSR has a long way to go before it is “good”.
- philipwhiuk 2y ago"Server-side-rendering" confused me for ages because I figured it must be some new fancy tech instead of 'what PHP has done from the beginning'. SSR isn't actually rendering anything of course.
- tiagod 2y agoIn the context of React it makes sense, as traditionally it's a client-side rendering thing. Until recently, a redundant render would run in the client once the js is loaded anyway, but I believe it's possible to skip that now.