4 ms·
Damn, Svelte is not on there. I'd be curious what the author thinks to it as an approach https://svelte.technology/ https://svelte.technology/
by fold_left 8y ago
Damn, Svelte is not on there. I'd be curious what the author thinks to it as an approach https://svelte.technology/ https://svelte.technology/
- nailer 8y agoI was about to say, this is precisely the reason Svelte exists. I rewrote my personal site in it a year ago [1], and the development experience was similar to a Vue or Ractive app, but with compilation (ie, the resulting webpage doesn't have Svelte included - it's just my app specifically compiled) the result was tiny. [1] https://mikemaccana.com https://mikemaccana.com, probably has a lot of small bugs since I spent my time working on more important things.
- KaoruAoiShiho 8y agoCouldn't SSR with later JS hydration be just as effective at getting instant startup?
- nailer 8y agoSvelte also does SSR (if you set it up, which I haven't bothered), but you don't have to pull down a whole framework, so the hydration step is much faster.
- KaoruAoiShiho 8y agoRight, but with SSR the other frameworks basically have no downside. Their loading is also instant. A 1 second long hydration is not a big deal.
- nailer 8y ago1000ms hydration may be a big deal, hydration may also take more than 1000ms.
- KaoruAoiShiho 8y agoWhat matters to people is the content loading and being able to see the page. For the majority of apps the hydration is almost irrelevant because the time it takes to read the page and decide to interact with it takes vastly more than 1000ms, though there could be exceptions. It's certainly the case for all the apps I've worked on.