4 ms·
"In many cases you might want part (or all) of your app to be served as static markup. Reasons can include rendering speed, supporting environments where JavaSc
by atirip 14y ago
"In many cases you might want part (or all) of your app to be served as static markup. Reasons can include rendering speed, supporting environments where JavaScript is missing (or disabled), or search engine optimization."
?!? Why would anyone, ever, serve APP as static pages to those having JS disabled. Web site, thousand times yes, but APP?
- keen 14y agoYou're right, it's a rare case. I will change that bit.
- deliminator 14y agoThere is a case for doing both, pre-rendering on the server, and rendering updates on the client. This approach is used by Google plus for example. I wrote a simple implementation that uses google closure templates to pre-render the page with dynamic content on the server, and to me the app felt more stable. This feeling may be entirely subjective, as I didn't make any actualy measurements. A counterargument may be that this approach does not scale and would overload a server resulting in worse stabilit/render-time in the end.