|
You are here |
blog.miguelgrinberg.com | ||
| | | | |
nguyenhuythanh.com
|
|
| | | | | Overview Generally, there are two ways of web rendering: the first is SSR, stands for Server-Side Rendering; the second is CSR, stands for Client-Side Rendering. Both come with different trade-offs. Someone has compared that to a cycle, where we first started with SSR, then moved to CSR/SPA as the client-side application state became complex. Because CSR has its problems, we (re)discovered SSR 1 with HTMX, or even NextJS SSR. There were many writing about issues of CSR and SPA 2 3, but I would summarize them essentially as a state synchronization problem between the client and the server that results in complexity 4. | |
| | | | |
lchandara.wordpress.com
|
|
| | | | | As covered inComet Programming: Using Ajax to Simulate Server Push, Comet is a Web application model that enables Web servers to send data to the client without having to explicitly request it. Hence, the Comet model provides an alternate mechanism to classical polling to update page content and/or data. In that article, we learned how... | |
| | | | |
www.quirksmode.org
|
|
| | | | | [AI summary] A comprehensive technical resource detailing JavaScript functions, objects, events, and the DOM for web developers. | |
| | | | |
antoinevastel.com
|
|
| | | Short NodeJS example that showcases how you can make HTTPS requests routed through HTTP proxies without using any external dependencies. | ||