4 ms·
Latency. Server-side rendered pages can display immediately; client-side ones need to wait for the JS to download before they show anything. This can be a sig
by nostrademons 12y ago
Latency. Server-side rendered pages can display immediately; client-side ones need to wait for the JS to download before they show anything. This can be a significant advantage for sites that are transactional or content-based in nature (eg. Google, weather, news, or Wikipedia).
- jeswin 12y agoYou can achieve weather, news, wiki levels of performance with client-side rendering. Although, today it depends on the device you're using.
- glimcat 12y agoExactly. Server-side vs. client-side rendering of HTML is just another optimization choice. Is it more important to shorten the time to display the current request, or to shorten the time for new pages to be rendered? Single-page apps marginally increase the current request's time-to-render in exchange for improving navigation between pages. For some purposes that provides a significant benefit, other times it doesn't.
- jebblue 12y agoMy view changed a few months ago. I think SPI (Single Page Application) is here to stay and is fast subsuming the web landscape: http://en.wikipedia.org/wiki/Single-page_application http://en.wikipedia.org/wiki/Single-page_application My tool of choice is jQuery Mobile. If it weren't for that I'd probably do AngularJS; whatever it takes to shift the processing to the client and make my life easier by not having to muck around in too much JavaScript code. The point being that this approach works just fine for document centric sites.