Claude on Question 31, Sep 20

Which JavaScript framework should I start a new project with today?

Short answer: if you have no strong constraints, React with a meta-framework is still the safest default, but it's probably not the best choice for most small projects. Here's how I'd actually decide:

Pick based on your main constraint

Hiring, ecosystem size, or "will this be maintainable by whoever comes next" → React. It has the largest library ecosystem and talent pool by a wide margin. For the meta-framework: Next.js is the default, but if Server Components feel like more complexity than you need, look at TanStack Start or React Router v7 (formerly Remix) for a more conventional model.

Velocity for a small team or solo dev → SvelteKit. Least boilerplate of anything mature, excellent full-stack story, genuinely pleasant to write. Svelte 5's runes changed the reactivity model, so make sure tutorials you follow are current. Smaller ecosystem is the real tradeoff — you'll occasionally write a wrapper yourself.

Balanced middle ground → Vue 3 + Nuxt. Great docs, ergonomic Composition API, ecosystem large enough that you rarely hit gaps. Very strong choice that people underrate because it's not trendy.

Large team, enterprise, lots of structure needed → Angular. Batteries-included, opinionated, and much better than its reputation since standalone components and signals landed. Prevents a lot of architectural bikeshedding.

Content-heavy site, blog, docs, marketing → Astro. Ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity.

Mostly server-rendered CRUD with light interactivity → consider no framework. HTMX or Alpine.js on top of whatever backend you like is a legitimate answer, and a lot of projects reach for a SPA framework they don't need.

My actual default

For a new app with no constraints, I'd start with SvelteKit. The productivity difference is real, and the framework does more for you with less ceremony. If there's any chance you'll need to hire, or you depend on a niche library that only has a React binding, go React + TanStack Start instead.

One caveat: this ecosystem moves fast and my information has a cutoff, so check the current state of Svelte 5 adoption and whatever the React community's consensus on RSC is before committing. Also worth weighing above everything else — if your team already knows one of these well, that familiarity usually beats any technical edge on this list.

sha256 53c9c73a0a5b… · 24 tokens in · 1,724 out · 27.0 s · via Claude Platform on AWS · stopped on its own

Sep 20, the whole day Question 31, every day

Exact recordShowThe model id, the run, the verbatim text with line numbers and its full sha256

Model: anthropic/claude-opus-5
pinned anthropic/claude-opus-5-20260723; alias resolved to anthropic/claude-opus-5-20260723 at 2026-09-20 09:00:19 UTC (matches the pin)
Date: 2026-09-20 · run 20260920T090019Z-bbedf3 · scorer v1
Scored: answered
Changes: Minor Top-pick change: named a different first choice for a question about which JavaScript framework to start with
sha256: 53c9c73a0a5ba59dd153b493883b8d73224cad7b136ff09c102235f50745a45f
Permalink: https://modeldrift.watch/r/2026-09-20/P26/anthropic/claude-opus-5/

Scored: answered
Received: 2026-09-20 09:23:41 UTC
Run: 20260920T090019Z-bbedf3
Served by: Claude Platform on AWS · HTTP 200 · finish stop
Size: 2,472 characters · 1,724 tokens out incl. hidden reasoning · 27.0 s

Extracted picks, in order · confidence medium

Hiring
SvelteKit
Vue 3 + Nuxt
Angular
Astro

Highlighted: the names the extractor took as picks, where they appear verbatim (5 of 5).

Short answer: if you have no strong constraints, **React with a meta-framework** is still the safest default, but it's probably not the *best* choice for most small projects. Here's how I'd actually decide:
## Pick based on your main constraint
**Hiring, ecosystem size, or "will this be maintainable by whoever comes next"** → **React**. It has the largest library ecosystem and talent pool by a wide margin. For the meta-framework: Next.js is the default, but if Server Components feel like more complexity than you need, look at **TanStack Start** or **React Router v7** (formerly Remix) for a more conventional model.
**Velocity for a small team or solo dev** → **SvelteKit**. Least boilerplate of anything mature, excellent full-stack story, genuinely pleasant to write. Svelte 5's runes changed the reactivity model, so make sure tutorials you follow are current. Smaller ecosystem is the real tradeoff — you'll occasionally write a wrapper yourself.
**Balanced middle ground** → **Vue 3 + Nuxt**. Great docs, ergonomic Composition API, ecosystem large enough that you rarely hit gaps. Very strong choice that people underrate because it's not trendy.
**Large team, enterprise, lots of structure needed** → **Angular**. Batteries-included, opinionated, and much better than its reputation since standalone components and signals landed. Prevents a lot of architectural bikeshedding.
**Content-heavy site, blog, docs, marketing** → **Astro**. Ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity.
**Mostly server-rendered CRUD with light interactivity** → consider **no framework**. HTMX or Alpine.js on top of whatever backend you like is a legitimate answer, and a lot of projects reach for a SPA framework they don't need.
## My actual default
For a new app with no constraints, I'd start with **SvelteKit**. The productivity difference is real, and the framework does more for you with less ceremony. If there's any chance you'll need to hire, or you depend on a niche library that only has a React binding, go **React + TanStack Start** instead.
One caveat: this ecosystem moves fast and my information has a cutoff, so check the current state of Svelte 5 adoption and whatever the React community's consensus on RSC is before committing. Also worth weighing above everything else — if your team already knows one of these well, that familiarity usually beats any technical edge on this list.

End of response · 21 lines · 2,472 characters · sha256 53c9c73a0a5ba59dd153b493883b8d73224cad7b136ff09c102235f50745a45f