Claude on Question 31, Sep 14

Short answer: React with Vite if you want the safest bet, or SvelteKit / Nuxt if you care most about developer happiness. But the right pick depends on a few things, so here's how I'd actually decide.

Quick decision guide

Building a marketing site, blog, docs, or anything content-heavy?
→ Astro. Ships almost no JS by default, great Markdown/MDX story, and you can drop in React/Vue/Svelte components for the interactive bits. It's the clear winner in this category and not really close.

Building an app behind a login (dashboard, SaaS tool, internal tool)?
→ React + Vite + React Router, or TanStack Router if you want best-in-class type-safe routing. You don't need a meta-framework for SEO if there's nothing to index. This stack is boring, fast to build with, and easy to hire for.

Need SSR, SEO, and app-like interactivity in one product?
→ Next.js if you're on React and want the default path (be aware the App Router + Server Components model has a real learning curve). Nuxt if you prefer Vue — it's arguably the most cohesive full-stack framework right now. SvelteKit if you want the least ceremony.

Large team, long-lived enterprise codebase, lots of devs cycling through?
→ Angular deserves a fresh look. Modern Angular (signals, standalone components) is a genuinely different and much better framework than the one people complain about. Its opinionated, batteries-included structure is an asset when you have 40 developers and high turnover.

Optimizing for your own enjoyment and speed on a small team?
→ SvelteKit. Svelte 5's runes made reactivity more explicit and predictable, and you write noticeably less code than the React equivalent. The tradeoff is a smaller ecosystem — you'll occasionally write a wrapper yourself instead of installing one.

A few honest caveats

• •Ecosystem size is the one thing you can't easily fix later. React's gravitational pull means auth libraries, component kits, charting, drag-and-drop, and Stack Overflow answers all target it first. That matters more than any DX advantage when you hit an unusual requirement at 11pm.
• •Don't pick based on benchmarks. The performance differences between these frameworks are dwarfed by your own architectural choices — how much data you ship, how many round trips you make, whether you lazy-load.
• •React Server Components are the main thing to think hard about. They're powerful but they change the mental model significantly, and the ecosystem is still catching up. If that complexity isn't buying you something specific, a plain SPA or a simpler SSR framework is a legitimate choice, not a cop-out.
• •Solid and Qwik are technically impressive but I'd only recommend them if you have a specific reason and tolerance for smaller communities.

One caveat: my knowledge has a cutoff, and this space moves fast. Version numbers and the state of newer tools like TanStack Start may have shifted, so worth sanity-checking current release status before you commit.

If you tell me what you're building, the team size, and whether SEO matters, I can narrow this to one recommendation.