8 ms·
What site are you criticizing exactly? The blog is a bunch of HTML served up with only the usual google panopticon JS, and is certainly not doing client-side re
by cmrx64 6y ago
What site are you criticizing exactly? The blog is a bunch of HTML served up with only the usual google panopticon JS, and is certainly not doing client-side rendering. HN is also a bunch of HTML with just a titch of JS - and little of it generates HTML (which would be client-side rendering). Tell me again, what are you complaining about?
- natch 6y agoRelax, I was complimenting the site, which performs beautifully on a mobile device. And rhetorically pointing out that it is rendered by browser technology (WebKit), which, last time I checked, was considered client side. But hey I could be wrong, so feel free to educate me.
- cmrx64 6y agoIn web dev parlance client side rendering refers to dynamically generating HTML from some data format (eg, serving a template and having the JS render it and add it to the DOM, instead of applying the template on the server and sending the resulting HTML). You're right that the browser's rendering engine ultimately does all the work of generating the images that get displayed, but that has to happen anyway and isn't a distinction that gets talked about (much) in web dev land.
- natch 6y agoOK I see,thank you.