Content
@
0 reply
0 recast
2 reactions
borodutch
@warpcastadmin.eth
gm folks, i wrote an article describing why i never use ssr and you shouldn't either criticism will be ignored but you will comment anyway won't you https://blog.borodutch.com/i-never-use-ssr-and-you-shouldnt-either/
21 replies
5 recasts
75 reactions
df
@df
wrong; everything old is new again - only SSR, never CSR, back to where we started: php ๐ The main problem with SSR was the complexity of writing isomorphic code and reasoning about state. With only server side that problem is solved. Turns out sending 300kB bundles of your (code split) JS on first request is slow
3 replies
0 recast
1 reaction
borodutch
@warpcastadmin.eth
ser, ssr initial load is always slower by magnitudes
1 reply
0 recast
1 reaction
df
@df
here's one counterexample to "ssr initial load is always slower by magnitudes" where not only is it not a magnitude slower, but it's faster. https://medium.com/walmartglobaltech/the-benefits-of-server-side-rendering-over-client-side-rendering-5d07ff2cefe8
2 replies
0 recast
1 reaction
borodutch
@warpcastadmin.eth
stop giving me theory i'm talking real world here
1 reply
0 recast
1 reaction
df
@df
"We compared three of our applications(home, category, and search) in SSR vs CSR. These are the chrome network screen grabs of the pages being rendered. Youโll notice that SSR renders faster, and that using CSR has the blank white page while loading." how much more real world do you want?
1 reply
0 recast
1 reaction