Back to blog
Thoughts

Why I keep choosing Svelte

Not a framework comparison. Just why it clicks for me after years of React and Vue.

#svelte#frontend#opinion

I’ve used React for years. I’ve used Vue. I’ve tried Angular once and we don’t talk about that.

Svelte is the one I keep coming back to.

It’s not about performance

Everyone talks about bundle size and virtual DOM overhead. That’s not why I choose it. I choose it because when I sit down to build something, I spend less time fighting the framework and more time solving the actual problem.

No useEffect dependency arrays. No useMemo to avoid re-renders that shouldn’t happen in the first place. No wrapping everything in useCallback because your child component re-renders when a parent state changes.

In Svelte, you write:

let count = $state(0)
let doubled = $derived(count * 2)

And it works. That’s it. No mental gymnastics about when things re-run.

The ecosystem is smaller (and that’s fine)

Yes, React has 50 date picker libraries. Svelte has 3. But I’ve never actually needed 50 options. I need one that works.

And when something doesn’t exist, you build it. That’s how my datagrid package happened. Needed a good data table for a project, existing options weren’t great for Svelte 5, so I built one.

Where I don’t use it

Big team that already knows React? I’ll use React. Need React Native? Obviously not Svelte. Client specifically asks for Next.js? Sure.

I’m not religious about tools. Svelte is just the one that gets out of my way the fastest when I’m building for myself or when I have the choice.

The honest part

My React knowledge is getting rusty. I don’t remember half the hooks API anymore. New React features come out and I think “Svelte already does this simpler.” Maybe I’m biased now. Probably. But I ship faster, so I don’t care.

tzezar. © 2026 Sebastian Drozd

built with svelte & too much coffee