The honest version of "which framework should I use in 2026" is boring: use React. It's the safe answer. The ecosystem is enormous, every other dev already knows it, and you will never get fired for choosing it. I went with Svelte + Astro instead. Not because React is bad — it isn't — but because for the kind of work I do, the tradeoff actually pencils out.
Why I picked it anyway
The pitch is simple: Svelte gets out of your way, and Astro ships less of it.
Svelte is a compiler, not a runtime. You write something close to plain HTML with logic in it, and it compiles to small, direct DOM updates. Svelte 5's runes ($state, $derived, $effect) killed the thing I hated most in React — the bookkeeping. No dependency arrays, no useMemo gymnastics, no stale-closure traps. State is state. Derived values derive. I spend my attention on the feature, not on babysitting the render cycle.
Astro handles the rest: ship zero JS by default, hydrate only the interactive islands. My pages are fast without me trying. The default is the optimized path.
Put together: less boilerplate, smaller bundles, a mental model that stays close to the platform. For a small team — or a team of one — that compounds.
Where it genuinely costs you
Here's the part nobody puts in the headline.
The ecosystem is smaller, and you feel it. React has a pre-built answer for almost everything. Need a date picker, a data grid, a rich-text editor, a charting library with ten years of edge cases ironed out? It exists, it's maintained, and there are three competing versions. In Svelte you'll often find a solution rather than the solution — or you'll build it yourself. Sometimes that's a feature (you understand your own code). Often it's just a tax you pay in hours.
Everyone else knows React. This is the one that bites teams, not solo projects. If I want to hand off code, hire, or bring in a contractor for a week, the React talent pool is the entire industry. The Svelte pool is a puddle by comparison. If your bet is "scale the team fast," React is the rational hedge. I'm betting the other way, and I know it's a bet.
AI tooling is measurably worse at Svelte. (This is the 2026 one.) Every coding assistant was trained on far more React than Svelte. Ask for a React component and it's fluent. Ask for Svelte and you get more mistakes, plus a nasty habit of generating outdated Svelte 4 patterns when you're on 5. The AI productivity boost everyone's riding? You get a thinner slice of it by default. I've clawed most of it back — but only by writing a pile of project-specific rules to teach the AI my patterns. React devs get that for free.
So who should actually pick Svelte?
Not everyone. My honest decision rule:
Pick React if you're hiring soon, building something with heavy third-party widget needs, or you want the AI tooling to carry maximum weight out of the box.
Pick Svelte + Astro if you're a small team or solo, you value a codebase you fully understand over one full of dependencies, you care about shipping fast and light, and you're willing to invest a little to make your tooling fluent in it.
I fall squarely in the second bucket, which is why I'm here. But I'd be lying if I said the first bucket was wrong. Most teams probably belong in it.
The part that makes this credible
Svelte didn't win because it's objectively better. It won for me, for my constraints, after I'd looked the costs in the eye and decided I could live with them. The smaller ecosystem, the thinner hiring pool, the AI tax — those are real, and I pay them every week.
That's the honest tradeoff. Anyone who tells you a 2026 framework choice is free of tradeoffs is selling something — or hasn't shipped enough to get the bill yet.