|
You are here |
simpleprogrammer.com | ||
| | | | |
jszym.com
|
|
| | | | | This blog has a comment section and it's powered by ActivityPub pixies. I share some thoughts about the pros and cons. | |
| | | | |
mydevpa.ge
|
|
| | | | | The power of a portfolio website really depends on you and the contents of the website. But having one is 10x better than not having one.... | |
| | | | |
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. | |
| | | | |
redwoodjs.com
|
|
| | | Redwood's preview of React Server Component support is now available! Follow this walkthrough to find out what's new and how to covert an app from GraphQL. | ||