Explore >> Select a destination
|
You are here 
|
blog.miguelgrinberg.com | ||
| | | | |
www.quirksmode.org
|
|
| | | | | ||
| | | | |
mark-story.com
|
|
| | | | | I recently decided to go down a rabbit hole of wanting to learn a new client side library. I was interested in learning more about libraries that aimed to have a minimal footprint even at the cost of providing a more modest API. For this site I have simple requirements, and I wanted to see how simple the 'simple' abstractions are these days. | |
| | | | |
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.trickster.dev
|
|
| | | Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting | ||
