Explore >> Select a destination
|
You are here 
|
blog.bloomca.me | ||
| | | | |
blog.javascripting.com
|
|
| | | | | It was around 2011 and I was working for a small company with the ambitious goal of building the world's sexiest cloud CRM [https://raynetcrm.com] product. To build a great product, you need great technologies. Fortunately, one of my colleagues was a tech maven who tried hard to stay | |
| | | | |
vishaltelangre.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. | |
| | | | |
github.com
|
|
| | | A curated list of vibe coding references, collaborating with AI to write code. - filipecalegario/awesome-vibe-coding | ||
