Posts
-
Svelte as a Mirror for the Frontend, Not an Idol
Less "is Svelte any good", more using it as a clean reference that shows what the frontend was meant to look like.
-
The Framework Server Layer Is Not Your BFF
Next, Nuxt, and SvelteKit can all run server logic — but convenience is not an architecture.
-
Where Does the HTML Come From: SSR, CSR, SSG, ISR on One Path
Stop memorising acronyms. Ask one question instead — when and where was the HTML the user just received actually generated.
-
Two Ways to Wire a BFF: htmx Returns Partials, SvelteKit Goes JSON
One call chain, two front ends — htmx partials for admin tables, JSON over SvelteKit only when the client needs to hold state
-
SvelteKit's Default SSR Worldview — and Where It Bites You
SvelteKit's SSR defaults are well-reasoned. They can also grind to a halt the moment your environment stops cooperating.
-
Svelte 5 Runes: Reactivity Out in the Open
Runes swap compiler-guessed reactivity for explicit reactive primitives. You trade a bit of memorisation for predictability.
-
Memory and Sync Primitives
Escape analysis, sync.Pool, and choosing among atomic, Mutex, RWMutex. Prerequisites for zero-allocation.