/explore
|
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. |
|
| | | | | ||
| | | | |
www.quirksmode.org
[AI summary] A comprehensive technical resource detailing JavaScript functions, objects, events, and the DOM for web developers. |
|
| | | | | ||
| | | | |
ponyfoo.com
[AI summary] This article explains Taunus, a lightweight Node.js framework that converts server-side rendered applications into progressive web apps supporting AJAX navigation and realtime updates. |
|
| | | | | ||
| | | | |
blog.hmpl-lang.dev
Hello everyone! In this article, I'll show you how to create reactive HTML interfaces without relying on heavy JavaScript frameworks like Vue or Angular. We'll explore how HMPL.js provides a lightweight alternative that achieves reactivity through server-side rendering while keeping your client-side code minimal. The Problem with JavaScript Frameworks In... |
|
| | | |||
