Claude on Question 31, Sep 30

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

Short answer: if you have no strong constraints, React + Next.js is the safest default — biggest ecosystem, most hiring options, most tutorials and AI-assistance trained on it. But "safest" isn't always "best," so here's how I'd actually decide:

By project type

Content-heavy site (blog, docs, marketing, e-commerce catalog) → Astro. Ships almost no JS by default, great SEO, and you can drop React/Vue/Svelte components into individual "islands" where you need interactivity.

Full-stack app that needs SEO or fast first load → Next.js (React), Nuxt (Vue), or SvelteKit. All three are mature. Pick based on which language model you enjoy more.

Dashboard or internal tool behind a login (SEO irrelevant) → skip the meta-framework overhead. Vite + React + TanStack Router + TanStack Query is a fantastic, boring, fast stack. SvelteKit in SPA mode is also great here.

Large team, long-lived enterprise app, heavy TypeScript → Angular is genuinely worth reconsidering. Signals and standalone components modernized it a lot, and its opinionated structure prevents the 12-different-patterns problem big teams get with React.

You want to enjoy writing code → Svelte 5 + SvelteKit. Least boilerplate, very clean reactivity model with runes, consistently tops developer-satisfaction surveys. Tradeoff: smaller ecosystem and fewer job listings.

Honest notes on the tradeoffs

•React's complexity has grown. Server Components, the client/server boundary, and caching semantics in Next.js are real learning costs. If you're solo and building a CRUD app, you may be paying for power you don't need.
•Vue/Nuxt is the underrated middle. Gentler curve than React, better docs than almost anyone, ecosystem large enough that you won't hit walls.
•Don't pick something with churn risk unless you enjoy that. Remix/React Router has had significant direction changes; TanStack Start is promising but newer. Fine for a side project, riskier for a client deliverable.

The thing that actually matters

Framework choice is one of the least consequential decisions in a new project. Your database schema, auth approach, and deployment story will cause you far more pain. Any of the options above will work fine for 95% of projects — so pick the one you or your team already know, and spend the saved decision energy elsewhere.

One caveat: my information has a cutoff date, and this ecosystem moves fast. Before committing, check current release status and recent activity for whichever one you pick — especially for the newer options.

What are you building? I can give a much more specific recommendation with that context.

sha256 77f397f2de00… · 24 tokens in · 1,924 out · 27.1 s · via Claude Platform on AWS · stopped on its own

Sep 30, 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-30 09:00:07 UTC (matches the pin)
Date: 2026-09-30 · run 20260930T090007Z-45ce12 · scorer v1
Scored: answered
Changes: Minor Reverted top-pick change: went back to its earlier list for a question about which JavaScript framework to start with
sha256: 77f397f2de00da2d6610cc1a898d4ba87efa2f5cf302bd77909bd21b3210611c
Permalink: https://modeldrift.watch/r/2026-09-30/P26/anthropic/claude-opus-5/

Scored: answered
Received: 2026-09-30 09:21:47 UTC
Run: 20260930T090007Z-45ce12
Served by: Claude Platform on AWS · HTTP 200 · finish stop
Size: 2,686 characters · 1,924 tokens out incl. hidden reasoning · 27.1 s

Extracted picks, in order · confidence medium

Astro
Next.js
Vite + React + TanStack Router + TanStack Query
Angular
Svelte 5 + SvelteKit

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

Short answer: **if you have no strong constraints, React + Next.js is the safest default** — biggest ecosystem, most hiring options, most tutorials and AI-assistance trained on it. But "safest" isn't always "best," so here's how I'd actually decide:
## By project type
**Content-heavy site** (blog, docs, marketing, e-commerce catalog) → **Astro**. Ships almost no JS by default, great SEO, and you can drop React/Vue/Svelte components into individual "islands" where you need interactivity.
**Full-stack app that needs SEO or fast first load** → **Next.js** (React), **Nuxt** (Vue), or **SvelteKit**. All three are mature. Pick based on which language model you enjoy more.
**Dashboard or internal tool behind a login** (SEO irrelevant) → skip the meta-framework overhead. **Vite + React + TanStack Router + TanStack Query** is a fantastic, boring, fast stack. SvelteKit in SPA mode is also great here.
**Large team, long-lived enterprise app, heavy TypeScript** → **Angular** is genuinely worth reconsidering. Signals and standalone components modernized it a lot, and its opinionated structure prevents the 12-different-patterns problem big teams get with React.
**You want to enjoy writing code** → **Svelte 5 + SvelteKit**. Least boilerplate, very clean reactivity model with runes, consistently tops developer-satisfaction surveys. Tradeoff: smaller ecosystem and fewer job listings.
## Honest notes on the tradeoffs
- **React's complexity has grown.** Server Components, the client/server boundary, and caching semantics in Next.js are real learning costs. If you're solo and building a CRUD app, you may be paying for power you don't need.
- **Vue/Nuxt is the underrated middle.** Gentler curve than React, better docs than almost anyone, ecosystem large enough that you won't hit walls.
- **Don't pick something with churn risk** unless you enjoy that. Remix/React Router has had significant direction changes; TanStack Start is promising but newer. Fine for a side project, riskier for a client deliverable.
## The thing that actually matters
Framework choice is one of the *least* consequential decisions in a new project. Your database schema, auth approach, and deployment story will cause you far more pain. Any of the options above will work fine for 95% of projects — so pick the one you or your team already know, and spend the saved decision energy elsewhere.
One caveat: my information has a cutoff date, and this ecosystem moves fast. Before committing, check current release status and recent activity for whichever one you pick — especially for the newer options.
What are you building? I can give a much more specific recommendation with that context.

End of response · 27 lines · 2,686 characters · sha256 77f397f2de00da2d6610cc1a898d4ba87efa2f5cf302bd77909bd21b3210611c