3 ms·
Yeah - I wrote https://www.beyonk.com https://www.beyonk.com in Nuxt first, and I've now rewritten it in Svelte (Sapper). There are some things which weren't r
by wirahx 7y ago
Yeah - I wrote https://www.beyonk.com https://www.beyonk.com in Nuxt first, and I've now rewritten it in Svelte (Sapper).
There are some things which weren't ready when I started, but I worked around them. The overall experience is that Svelte results in faster pages, less code, more predictability, faster builds... overall, it's a better experience.
- vimota 7y agoOther than performance, was the developer experience any different? Just curious!
- exclipy 7y agoNice. I like the SSR and that subsequent page loads are basically just a 5KB fetch of pure content in JSON. But if I go to a content page (eg. https://www.beyonk.com/uk/6Gb_Kj/guided-ascent-of-curved-ridge https://www.beyonk.com/uk/6Gb_Kj/guided-ascent-of-curved-rid...), I see that the response is a 286KB blob, mostly consisting of CSS. If I reload the page, I redownload that 286KB blob. Wouldn't it be better to serve the CSS separately so it can be cached across sessions?