Claude on Question 31, Sep 11

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

Default answer: React with Next.js, mostly for boring reasons — the largest ecosystem, the most libraries with first-class support, the easiest hiring, and the most training data behind AI coding tools, which matters more than it used to. If you have no strong preferences and the project might grow or gain collaborators, this is the lowest-regret choice.

That said, I'd deviate in a few common situations:

Content-heavy site (marketing, docs, blog, e-commerce catalog) — use Astro. It ships almost no JS by default, and you can drop in React/Vue/Svelte components for the interactive bits. Next.js is overkill here and you'll fight it.

Solo project, and you care about enjoying the work — use SvelteKit. Less ceremony, less boilerplate, a genuinely coherent mental model, and excellent docs. Svelte 5's runes cleaned up the reactivity story. The tradeoff is a smaller component/library ecosystem, so you'll occasionally build things yourself.

Middle ground — Vue with Nuxt. More approachable than React, a bigger ecosystem than Svelte, and Nuxt is arguably better-designed than Next.js as a framework. It's just less dominant in North American job markets.

Enterprise, large team, long-lived app — Angular is a reasonable pick despite its reputation. It's opinionated in ways that help big teams, and signals plus standalone components made it far less painful than the 2016 version people remember.

Mostly server-rendered pages with sprinkles of interactivity — consider not using a framework. Your backend's templating plus HTMX or Alpine.js may be all you need, and you'll skip an enormous amount of build tooling.

One honest caveat on my main recommendation: Next.js's App Router and React Server Components introduced real complexity, and the "where does this code run" question trips up a lot of people. If that sounds unappealing and you don't need the ecosystem, SvelteKit or Nuxt will feel much better.

The meta-point: framework choice matters less than it feels like it does while you're deciding. Data modeling, auth, and deployment will cause you far more pain than any of these options. Pick one in the next hour and start building.

(Worth verifying current versions and release status — this space moves fast and my information has a cutoff.)

sha256 c36893ff48f0… · 24 tokens in · 1,570 out · 25.7 s · via Claude Platform on AWS · stopped on its own

Sep 11, 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-11 09:00:01 UTC (matches the pin)
Date: 2026-09-11 · run 20260911T090002Z-da0dd3 · 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: c36893ff48f09021994d658b7f07c5e941ed0cceac76eefab03098898c07ceef
Permalink: https://modeldrift.watch/r/2026-09-11/P26/anthropic/claude-opus-5/

Scored: answered
Received: 2026-09-11 09:29:35 UTC
Run: 20260911T090002Z-da0dd3
Served by: Claude Platform on AWS · HTTP 200 · finish stop
Size: 2,307 characters · 1,570 tokens out incl. hidden reasoning · 25.7 s

Extracted picks, in order · confidence medium

Default answer React with Next.js
Astro
SvelteKit
Vue with Nuxt
Enterprise

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

**Default answer: React with Next.js**, mostly for boring reasons — the largest ecosystem, the most libraries with first-class support, the easiest hiring, and the most training data behind AI coding tools, which matters more than it used to. If you have no strong preferences and the project might grow or gain collaborators, this is the lowest-regret choice.
That said, I'd deviate in a few common situations:
**Content-heavy site** (marketing, docs, blog, e-commerce catalog) — use **Astro**. It ships almost no JS by default, and you can drop in React/Vue/Svelte components for the interactive bits. Next.js is overkill here and you'll fight it.
**Solo project, and you care about enjoying the work** — use **SvelteKit**. Less ceremony, less boilerplate, a genuinely coherent mental model, and excellent docs. Svelte 5's runes cleaned up the reactivity story. The tradeoff is a smaller component/library ecosystem, so you'll occasionally build things yourself.
**Middle ground** — **Vue with Nuxt**. More approachable than React, a bigger ecosystem than Svelte, and Nuxt is arguably better-designed than Next.js as a framework. It's just less dominant in North American job markets.
**Enterprise, large team, long-lived app** — **Angular** is a reasonable pick despite its reputation. It's opinionated in ways that help big teams, and signals plus standalone components made it far less painful than the 2016 version people remember.
**Mostly server-rendered pages with sprinkles of interactivity** — consider not using a framework. Your backend's templating plus HTMX or Alpine.js may be all you need, and you'll skip an enormous amount of build tooling.
One honest caveat on my main recommendation: Next.js's App Router and React Server Components introduced real complexity, and the "where does this code run" question trips up a lot of people. If that sounds unappealing and you don't need the ecosystem, SvelteKit or Nuxt will feel much better.
The meta-point: framework choice matters less than it feels like it does while you're deciding. Data modeling, auth, and deployment will cause you far more pain than any of these options. Pick one in the next hour and start building.
(Worth verifying current versions and release status — this space moves fast and my information has a cutoff.)

End of response · 19 lines · 2,307 characters · sha256 c36893ff48f09021994d658b7f07c5e941ed0cceac76eefab03098898c07ceef