The Cyclical Fashion of Web Rendering
Description
A two-panel meme arranged vertically to illustrate a cycle. The top panel features the text 'Render on client' above an image of a person wearing modern, tight-fitting skinny jeans. The bottom panel displays the text 'Render on server' above a person in loose, baggy jeans reminiscent of 90s fashion. Two large, curved black arrows connect the panels, forming a circle to indicate a recurring cycle. A red map pin icon with the text 'YOU ARE HERE' points to the arrow leading from 'Render on server' back up to 'Render on client', signifying the current industry trend. The meme humorously compares the shifting paradigms of web rendering to fashion trends. Client-side rendering (CSR), popularized by frameworks like React and Angular, is depicted as the modern 'skinny jeans' style. The older method, server-side rendering (SSR), is equated with the 'outdated' baggy jeans. The joke, highlighted by the 'YOU ARE HERE' marker, is that the tech industry is currently cycling back to SSR for its performance and SEO benefits, making the old style fashionable once again
Comments
26Comment deleted
We've finally completed the great circle of webdev: from server-rendered pages, to client-side monoliths, and back to server-rendered pages but this time with 500MB of node_modules to do it
I’m hanging on to my early-2000s JSP codebase - fashion says it’ll be avant-garde again by the next quarterly roadmap
After spending years migrating from server-rendered monoliths to SPAs for that 'modern feel', we're now back to SSR with Next.js and calling it innovation - just like how baggy jeans from 1995 are somehow trendy again, except this time we're pretending the extra bundle size is actually good for SEO
The eternal rendering debate visualized: client-side gives you that sleek, tailored SPA experience, while server-side delivers the entire wardrobe upfront - because nothing says 'optimized user experience' like shipping 2MB of hydrated HTML that makes your lighthouse score look like a fashion disaster from 2003. At least with SSR, your SEO crawlers can see you're wearing *something* before JavaScript decides to show up fashionably late
CSR: sleek SPA dreams until hydration bloats you into SSR dad jeans
After a decade migrating from SPAs to SSR and now RSC, I’ve learned rendering is just a fashion cycle - only the jeans change and the egress bill gets tighter
After a decade of SPAs, we rebranded PHP as edge‑rendered React - same HTML, new hydration tax and a larger platform team
could someone explain Comment deleted
+ Comment deleted
Guys, on which side colors seams more naturally? Comment deleted
right Comment deleted
right Comment deleted
there is a problem with your fps Comment deleted
error in fps aside isn't that too low for just rendering this shader ? Comment deleted
It because two running applications Comment deleted
right is more natural, left is more interesting Comment deleted
Define "natural" and the intent of this picture. If this is about perceptionally uniform transitions between primary colors, then you must define viewing conditions — at least the source colorspace, like sRGB. 🧐 Comment deleted
What problem? Comment deleted
0.166 ms delta time is more like 6FPS Comment deleted
Dude in one second we have 1000 milliseconds. If we divide 1000 by 0.166, we will have about 6024 Comment deleted
oh shit my bad Comment deleted
I was thinking about 60 fps and 0.116 seconds 💀 Comment deleted
I have about 12000 fps, when one runs Comment deleted
I cannot get more due to high latency on present call Comment deleted
don't got it, explain please Comment deleted
On the left side there are unorm, on the right is sRGB. Both 32 bits and non linear Comment deleted