Rendering doesn't have to mean generating bitmap pixels. In any case, the pixels you generate would get compressed before going over the wire. The HTML document can be viewed as an especially convoluted vector representation of the scene (in this case, a tree) that compresses things like text very efficiently.
RDP does stuff like this to more efficiently transmit window contents over the wire, AFAIK - they're not just sending bitmaps.
Wholeheartedly agree. I actually tweeted out this morning a suggestion: HSR (Hydrated server rendering) .. i think that encapsulates the difference pretty well.. although CHSR would be more accurate, but "Client" is implied when talking about "hydration" imo
Re:A Gentle Introduction to SSR
by tatersolid on Tuesday May 03, 2022 @09:36PM
(#31255825)
Back in the 90s we used to call outputting HTML from a dynamic server process “serialization”.
Get off my lawn.
Re:A Gentle Introduction to SSR
by andthenwhat on Tuesday May 03, 2022 @07:54AM
(#31247200)
Agree. I thought I was clicking on an article about screen-space reflections in 3D rendering, although CGI and Perl were around long before that so they win the race for that acronym.
Offloading the actual rendering-engine from gluing together the HTML document from parts fetched or produced by Javascript prior to actually rendering the webpage can probably be a good idea in some instances. But this is hardly a new technique. Using Javascript to do it doesn't make it something different than PHP or the good old CGI scripts in Perl/Python.