Hacker News new | ask | show | jobs
by dimgl 451 days ago
As much as I appreciate Svelte, the React devex is unmatched. I built a client-side app using Wails with Svelte 5 and I found myself wanting React's seamless devex and vast ecosystem. Once I migrated over to React it was like a huge handicap was lifted.

Svelte is great. But if you're in a time crunch and you don't have a specific technical requirement that makes React a bad match, I don't think Svelte is worth it. A big part of the Svelte ecosystem is still using Svelte stores, and I found the "one component per file" paradigm to be a bit limiting.
2 comments
prophesi 451 days ago
> A big part of the Svelte ecosystem is still using Svelte stores

Just a nitpick, with runes in Svelte 5, stores have largely become obsolete. $state, $derived, and $effect replace most of the needs people would normally use stores for.

link
dimgl 451 days ago
That's right; but a lot of packages, like Superforms, use stores.
link
prophesi 451 days ago
That's fair. The major libraries I use migrated to runes even before Svelte 5 was officially released. You can use runes with Superforms[0] as any store-based API can have rune-based reactivity passed to it, but it sounds like using runes internally is a V3 milestone.

[0] https://superforms.rocks/examples?tag=runes

link
DimmieMan 451 days ago
I think i'm about a chapter behind you.

I'll add devex extends to TSX/JSX itself too, the editor support and language server experience is miles ahead. Alternative formatters/linters like Deno, Biome, oxc etc. all have great support out of the box too, not so much for svelte.

For when react is a bad match; I'm investigating solid instead for this reason.

The svelte ecosystem is in a particularly unfortunate spot right now comprising of single/few author projects that were starting to stabilise but now have a svelte 4 -> 5 migration shaking things up.

link