Explore >> Select a destination
|
You are here 
|
ponyfoo.com | ||
| | | | |
fantinel.dev
|
|
| | | | | Progressive Enhancement isn't just another web jargon; it's a guiding principle shaping modern web development. | |
| | | | |
www.stillbreathing.co.uk
|
|
| | | | | [AI summary] A weekly curated list of links covering web development topics such as performance, accessibility, mobile design, JavaScript, and open source. | |
| | | | |
blog.risingstack.com
|
|
| | | | | In this article, we'll focus on the most popular JavaScript frameworks, and explore why they're either loved or disliked by developers. | |
| | | | |
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. | ||
