4 ms·
No? Each client may be receiving the same document, but based on their device, view port, preferences, etc… the rendered result may be different. Either way, t
by guhidalg 4y ago
No? Each client may be receiving the same document, but based on their device, view port, preferences, etc… the rendered result may be different.
Either way, the measurement of Joules/page is likely to be such an astronomically small number compared to the constant cost of simply having a server at all IMO.
- Schiendelman 4y agoThe number of devices is very small. I’m sure you get a number of different window sizes, but within a range, you can very slightly scale.
- guhidalg 4y agoAre you suggesting we give up on rendering layouts that respond to different window sizes, display resolutions, and zoom levels? I think what you’re suggesting is that clients requesting websites should receive essentially an image of the website with limited interactivity, but that’s not going to make anyone that’s ever used a website satisfies in C.E. 2023.
- mkl 4y agoYou can make web pages responsive to "different window sizes, display resolutions, and zoom levels" with no JavaScript at all, so that's clearly not what they're suggesting.
- guhidalg 4y agoThat’s true, but it’s not like translating HTML into a bitmap for a display is some spontaneous process that happens for free. Your browser is anyone going to interpret all that HTML and CSS, and your users are going to click on buttons and submit forms that require changing that HTML and CSS. Whether that happens through JavaScript or SSR is bike-shedding: processing will be done, computation is needed, we can sit here and argue about how the web front end world sucks but billions of users expect interactive web applications that are very difficult to deliver without JavaScript.