MODELDRIFT.WATCH

Sep 12 · Day 3

MINOR · CLAUDE · QUESTION 31

Claude named a different first choice for a question about which JavaScript framework to start with.

Why it’s minor

Which products a model recommends is read out of its answer by the least reliable part of our scorer, so compare the two answers before reading much into this.

The full answers

Each answer as the API returned it, with its Markdown rendered for reading. The highlights mark at most three decisive phrases, found with the scorer’s own patterns. Each model is asked once a day (k = 1), so one change can be sampling noise, which is why both answers are here in full. How scoring works.

Asked verbatim · Question 31

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

SEP 11beforePermalink

Picks read from the answer, in order
  1. Default answer React with Next.js
  2. Astro
  3. SvelteKit
  4. Vue with Nuxt
  5. Enterprise

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.)

SEP 12afterPermalink

Picks read from the answer, in order
  1. Astro
  2. Svelte + SvelteKit
  3. Angular
  4. React Router v7

Short answer: React with a meta-framework is the safest default, and for most people that means Next.js. Biggest ecosystem, most libraries, most hiring options, most answers when you get stuck.

But "safest" isn't always "best." Here's where I'd deviate:

Content-heavy site (blog, docs, marketing) → Astro. It ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity. For this category it's not a close call.

You want the nicest developer experience and don't specifically need React's ecosystem size → Svelte + SvelteKit or Vue + Nuxt. Both are noticeably less ceremony than React. Svelte 5's runes are elegant; Vue's Composition API is mature and the docs are excellent. The tradeoff is a smaller ecosystem and fewer Stack Overflow hits at 2am.

Large team, long-lived enterprise app, high turnover → Angular. Strong conventions mean less bikeshedding and easier onboarding, and it comes with routing, forms, HTTP, and DI in the box.

You just need some interactivity on a mostly server-rendered app → consider skipping a framework. HTMX, Alpine, or plain JS with a server-side templating language. A lot of projects reach for React and inherit a build pipeline and hydration model they never needed.

If you pick React, one real decision: Next.js is the default but has become fairly complex (App Router, Server Components, and some coupling to Vercel's deployment model). If that friction bothers you, React Router v7 or TanStack Start are less magical alternatives with more conventional mental models.

Two honest caveats. First, my information has a cutoff, so check current versions and release notes before committing — this space moves fast. Second, and more importantly: framework choice matters less than it feels like it does. Any of these will work fine for almost any project. Data modeling, auth, deployment, and testing will cost you far more time than your view layer. Pick the one you or your team will actually be productive in and move on.

If you tell me what you're building, team size, and your existing experience, I can give you a straight recommendation instead of a decision tree.

Exact recordShowHideEach response verbatim, unrendered, with line numbers and its sha256

Before baseline

2026-09-11 permalink

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
  1. Default answer React with Next.js
  2. Astro
  3. SvelteKit
  4. Vue with Nuxt
  5. 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

After this run

2026-09-12 permalink

Scored
answered
Received
2026-09-12 09:23:14 UTC
Run
20260912T090021Z-c0c86e
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,214 characters · 1,727 tokens out incl. hidden reasoning · 25.8 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Svelte + SvelteKit
  3. Angular
  4. React Router v7

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

Short answer: **React with a meta-framework** is the safest default, and for most people that means Next.js. Biggest ecosystem, most libraries, most hiring options, most answers when you get stuck.
But "safest" isn't always "best." Here's where I'd deviate:
**Content-heavy site** (blog, docs, marketing) → **Astro**. It ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity. For this category it's not a close call.
**You want the nicest developer experience** and don't specifically need React's ecosystem size → **Svelte + SvelteKit** or **Vue + Nuxt**. Both are noticeably less ceremony than React. Svelte 5's runes are elegant; Vue's Composition API is mature and the docs are excellent. The tradeoff is a smaller ecosystem and fewer Stack Overflow hits at 2am.
**Large team, long-lived enterprise app, high turnover** → **Angular**. Strong conventions mean less bikeshedding and easier onboarding, and it comes with routing, forms, HTTP, and DI in the box.
**You just need some interactivity on a mostly server-rendered app** → consider skipping a framework. HTMX, Alpine, or plain JS with a server-side templating language. A lot of projects reach for React and inherit a build pipeline and hydration model they never needed.
**If you pick React, one real decision:** Next.js is the default but has become fairly complex (App Router, Server Components, and some coupling to Vercel's deployment model). If that friction bothers you, **React Router v7** or **TanStack Start** are less magical alternatives with more conventional mental models.
Two honest caveats. First, my information has a cutoff, so check current versions and release notes before committing — this space moves fast. Second, and more importantly: framework choice matters less than it feels like it does. Any of these will work fine for almost any project. Data modeling, auth, deployment, and testing will cost you far more time than your view layer. Pick the one you or your team will actually be productive in and move on.
If you tell me what you're building, team size, and your existing experience, I can give you a straight recommendation instead of a decision tree.

End of response · 17 lines · 2,214 characters · sha256 bb6f28b250b3c24f4317ceac977a99c32c02f06f164d2a8c9277947fd9ab475c

Record detailsShowHideModel version, runs, baseline, triage, permalink, event ID
Model
anthropic/claude-opus-5
pinned anthropic/claude-opus-5-20260723; alias resolved to anthropic/claude-opus-5-20260723 at 2026-09-12 09:00:20 UTC (matches the pin)
Prompt
Question 31: P26 (recommendation)
Why this question
Tools for building websites change fast, so the answer shows how current a model’s knowledge is.
Change
first extracted pick differs from the baseline's (full lists below)
Baseline
2 prior days with data; 1 matched the baseline value (2026-09-11)
Responses
before 2026-09-11 09:29:35 UTC, run 20260911T090002Z-da0dd3; after 2026-09-12 09:23:14 UTC, run 20260912T090021Z-c0c86e
Detected
2026-09-12 · run 20260912T090021Z-c0c86e, started 2026-09-12 09:00:21 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-12/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-12:P26:anthropic/claude-opus-5:pick_change:picks.top

Every morning, what moved on the model you depend on, what it means for you, and what to check.

$9 a month. Cancel any time. The next one tomorrow morning.

Get the daily brief

$99 once, for as long as modeldrift.watch runs. The first 100 buyers.

The record stays free. The brief is the reading of it.