Claude on Question 31, Sep 27
Which JavaScript framework should I start a new project with today?Short answer: if you have no strong constraints, React with Vite (add React Router if you need routing) or Next.js if you need server rendering. It's the safest default — biggest ecosystem, easiest hiring, most answers when you get stuck. But the "right" pick depends a lot on what you're building:
By use case
- •Content-heavy site (blog, docs, marketing, e-commerce storefront): Astro. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
- •Dashboard / SPA with no SEO needs: Vite + React (or Vue). Skip the meta-framework — you don't need server components or SSR complexity for an app behind a login.
- •Full-stack app needing SSR, routing, data loading: Next.js, Nuxt (Vue), or SvelteKit. Next has the most resources and hosting support; Nuxt and SvelteKit are generally considered nicer to work with day to day.
- •Best developer experience, small team: SvelteKit or Nuxt. Less boilerplate, less ceremony, genuinely pleasant. Trade-off is a smaller ecosystem and hiring pool.
- •Large enterprise team, long-lived codebase: Angular. Opinionated and batteries-included, which is a feature when 40 people touch the code. It's improved a lot recently (signals, standalone components).
- •Web + native mobile from one codebase: React (via React Native / Expo). This basically decides it for you.
- •Adding interactivity to an existing Rails/Laravel/Django app: don't reach for a SPA framework. Use Inertia.js (with Vue or React), HTMX, or the framework's native tooling (Hotwire/Turbo, Livewire).
The honest meta-answer
Team familiarity beats framework quality almost every time. If you or your team already know one of these well, use that. All the major options are capable of building essentially any app; the differences show up in bundle size and ergonomics, not in what's possible.
The decision that actually matters more than framework choice is your rendering model — static, SSR, SPA, or a mix. Pick that based on SEO and performance needs first, then choose the framework that does it well.
Caveats
- •My knowledge has a cutoff, and this space moves fast. Check current release notes before committing — versions and best practices may have shifted.
- •Avoid picking something very new or niche (Qwik, Solid, etc.) for a project you need to maintain for years unless you specifically want their tradeoffs and can live with a thin ecosystem.
If you tell me what you're building, team size, and whether you need SEO or native mobile, I can narrow this to one recommendation.
Exact recordShowHideThe model id, the run, the verbatim text with line numbers and its full sha256
- Scored
- answered
- Received
- 2026-09-27 09:22:31 UTC
- Run
- 20260927T090007Z-7adb14
- Served by
- Claude Platform on AWS · HTTP 200 · finish stop
- Size
- 2,654 characters · 1,850 tokens out incl. hidden reasoning · 27.7 s
Extracted picks, in order · confidence medium
- Astro
- Dashboard / SPA with no SEO needs
- Next.js
- SvelteKit
- Angular
- React
- Inertia.js
Highlighted: the names the extractor took as picks, where they appear verbatim (7 of 7).
Short answer: **if you have no strong constraints, React with Vite (add React Router if you need routing) or Next.js if you need server rendering.** It's the safest default — biggest ecosystem, easiest hiring, most answers when you get stuck. But the "right" pick depends a lot on what you're building:
**By use case**
- **Content-heavy site** (blog, docs, marketing, e-commerce storefront): **Astro**. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
- **Dashboard / SPA with no SEO needs**: **Vite + React** (or Vue). Skip the meta-framework — you don't need server components or SSR complexity for an app behind a login.
- **Full-stack app needing SSR, routing, data loading**: **Next.js**, **Nuxt** (Vue), or **SvelteKit**. Next has the most resources and hosting support; Nuxt and SvelteKit are generally considered nicer to work with day to day.
- **Best developer experience, small team**: **SvelteKit** or **Nuxt**. Less boilerplate, less ceremony, genuinely pleasant. Trade-off is a smaller ecosystem and hiring pool.
- **Large enterprise team, long-lived codebase**: **Angular**. Opinionated and batteries-included, which is a feature when 40 people touch the code. It's improved a lot recently (signals, standalone components).
- **Web + native mobile from one codebase**: **React** (via React Native / Expo). This basically decides it for you.
- **Adding interactivity to an existing Rails/Laravel/Django app**: don't reach for a SPA framework. Use **Inertia.js** (with Vue or React), **HTMX**, or the framework's native tooling (Hotwire/Turbo, Livewire).
**The honest meta-answer**
Team familiarity beats framework quality almost every time. If you or your team already know one of these well, use that. All the major options are capable of building essentially any app; the differences show up in bundle size and ergonomics, not in what's possible.
The decision that actually matters more than framework choice is your **rendering model** — static, SSR, SPA, or a mix. Pick that based on SEO and performance needs first, then choose the framework that does it well.
**Caveats**
- My knowledge has a cutoff, and this space moves fast. Check current release notes before committing — versions and best practices may have shifted.
- Avoid picking something very new or niche (Qwik, Solid, etc.) for a project you need to maintain for years unless you specifically want their tradeoffs and can live with a thin ecosystem.
If you tell me what you're building, team size, and whether you need SEO or native mobile, I can narrow this to one recommendation.
End of response · 24 lines · 2,654 characters · sha256 b10aa9370f572e61fa432b49fa7ad53f621575dc4d1deb438db735f5f167bd57