MODELDRIFT.WATCH

Sep 17 · Day 8

MINOR · CLAUDE · QUESTION 31

Claude changed its list 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 16beforePermalink

Picks read from the answer, in order
  1. React

Short answer: React, unless you have a specific reason not to. Not because it's the best-designed framework — it isn't — but because ecosystem depth, hiring, library availability, and documentation mass make it the lowest-risk default. Then the more useful question is which React setup, and that depends on what you're building:

SPA behind a login (dashboard, internal tool, admin panel): React + Vite, with TanStack Router and TanStack Query. Skip Next.js here. You don't need SSR, and the App Router's complexity is pure cost when SEO doesn't matter.

Public-facing site that needs SSR/SEO: Next.js. It's the most battle-tested option and the default for good reason. Two honest caveats: React Server Components have a real learning curve and the mental model is still a moving target, and there's meaningful gravity toward deploying on Vercel — self-hosting works but is noticeably less smooth.

Content-heavy site (blog, docs, marketing): Astro. Ships almost no JavaScript by default, excellent Markdown/MDX story, and you can drop in React or Svelte components as islands where you actually need interactivity. Using Next.js for a blog is overkill.

Small team, greenfield, DX matters more than ecosystem size: SvelteKit. Genuinely more pleasant to write than React — less boilerplate, less ceremony. The tradeoff is a smaller library ecosystem, so you'll occasionally build things yourself that would be npm install in React-land.

Large enterprise team with many developers: Angular is a defensible choice. Strong conventions and batteries included means less bikeshedding across a big org.

Team already knows Vue: Nuxt. Fine framework, but rarely worth switching to if you don't have existing Vue expertise.

One thing to avoid: very young frameworks for anything you plan to maintain for years. A few promising ones are still stabilizing their APIs, and you don't want to absorb breaking changes as a side quest.

Worth saying plainly — the framework choice is one of the more reversible and less consequential decisions you'll make. Your data layer, auth provider, deployment target, and whether you actually need SSR will all shape the project more than React vs. Svelte. A boring choice you ship beats an optimal choice you research for three weeks.

My information has a cutoff, so verify current release status and versions before committing — this ecosystem moves fast.

If you tell me what you're building, team size, and whether SEO matters, I can give you a more specific recommendation.

SEP 17afterPermalink

Picks read from the answer, in order
  1. React
  2. Astro
  3. Next.js
  4. SvelteKit
  5. Angular

Short answer: React, via Vite for a SPA or Next.js if you need SSR/SEO. That's the safe default in 2025 because of ecosystem size, hiring, library availability, and the sheer volume of documentation and examples. But a few scenarios point elsewhere:

Pick by what you're building:

  • •Content-heavy site (blog, docs, marketing, e-commerce catalog): Astro. Ships almost no JS by default, and you can drop in React/Svelte/Vue components as islands where you need interactivity. Using a full app framework for this is overkill.
  • •Dashboard / internal tool / app behind a login: Vite + React + React Router. You don't need SSR, and skipping Next.js avoids a lot of complexity around server components, caching, and deployment.
  • •Public app that needs SEO and fast first loads: Next.js or Nuxt (Vue). Both are mature and have good hosting stories.
  • •Small team, you value DX and speed of writing code: SvelteKit. Less boilerplate, genuinely pleasant, smaller bundles. Trade-off is a thinner ecosystem — you'll occasionally write your own wrapper for something React has three options for.
  • •Large team, enterprise, long-lived codebase: Angular. Modern Angular (signals, standalone components) is much better than its old reputation suggests, and its opinionated structure and batteries-included tooling are real advantages when 30 people touch the same repo.
  • •Web + mobile from one skillset: React, so you can reuse knowledge with React Native.

Two things that matter more than the framework choice:

  • 1.Your rendering strategy. SPA vs. SSR vs. static generation affects your architecture, hosting cost, and debugging experience far more than React vs. Vue does. Decide this deliberately rather than inheriting it from a framework's defaults.
  • 2.What you or your team already know. Familiarity with a "worse" framework beats learning a "better" one on a real deadline. Frameworks converge on the same ideas anyway — components, reactive state, file-based routing.

Worth avoiding: starting with Solid or Qwik unless you specifically want their architectural properties and are comfortable being an early adopter. They're technically impressive but you'll hit gaps.

One caveat: my information has a cutoff, so check current versions and release notes before committing — Next.js in particular moves fast and has had some rough migrations. The broad landscape above has been stable for a while, though.

What are you building? I can give a more specific recommendation.

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

Before baseline

2026-09-16 permalink

Scored
answered
Received
2026-09-16 09:24:30 UTC
Run
20260916T090004Z-fdcf7b
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,542 characters · 2,272 tokens out incl. hidden reasoning · 32.9 s
Extracted picks, in order · confidence low
  1. React

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

Short answer: **React**, unless you have a specific reason not to. Not because it's the best-designed framework — it isn't — but because ecosystem depth, hiring, library availability, and documentation mass make it the lowest-risk default. Then the more useful question is *which React setup*, and that depends on what you're building:
**SPA behind a login** (dashboard, internal tool, admin panel): React + Vite, with TanStack Router and TanStack Query. Skip Next.js here. You don't need SSR, and the App Router's complexity is pure cost when SEO doesn't matter.
**Public-facing site that needs SSR/SEO**: Next.js. It's the most battle-tested option and the default for good reason. Two honest caveats: React Server Components have a real learning curve and the mental model is still a moving target, and there's meaningful gravity toward deploying on Vercel — self-hosting works but is noticeably less smooth.
**Content-heavy site** (blog, docs, marketing): Astro. Ships almost no JavaScript by default, excellent Markdown/MDX story, and you can drop in React or Svelte components as islands where you actually need interactivity. Using Next.js for a blog is overkill.
**Small team, greenfield, DX matters more than ecosystem size**: SvelteKit. Genuinely more pleasant to write than React — less boilerplate, less ceremony. The tradeoff is a smaller library ecosystem, so you'll occasionally build things yourself that would be `npm install` in React-land.
**Large enterprise team with many developers**: Angular is a defensible choice. Strong conventions and batteries included means less bikeshedding across a big org.
**Team already knows Vue**: Nuxt. Fine framework, but rarely worth switching *to* if you don't have existing Vue expertise.
One thing to avoid: very young frameworks for anything you plan to maintain for years. A few promising ones are still stabilizing their APIs, and you don't want to absorb breaking changes as a side quest.
Worth saying plainly — the framework choice is one of the more reversible and less consequential decisions you'll make. Your data layer, auth provider, deployment target, and whether you actually need SSR will all shape the project more than React vs. Svelte. A boring choice you ship beats an optimal choice you research for three weeks.
My information has a cutoff, so verify current release status and versions before committing — this ecosystem moves fast.
If you tell me what you're building, team size, and whether SEO matters, I can give you a more specific recommendation.

End of response · 21 lines · 2,542 characters · sha256 239eec192e4e4e8722076f01f4b1b7b650399f6a0feeac8e3a46104dc40b97f6

After this run

2026-09-17 permalink

Scored
answered
Received
2026-09-17 09:24:55 UTC
Run
20260917T090022Z-136fc3
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,540 characters · 1,694 tokens out incl. hidden reasoning · 25.2 s
Extracted picks, in order · confidence medium
  1. React
  2. Astro
  3. Next.js
  4. SvelteKit
  5. Angular

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

Short answer: **React, via Vite for a SPA or Next.js if you need SSR/SEO.** That's the safe default in 2025 because of ecosystem size, hiring, library availability, and the sheer volume of documentation and examples. But a few scenarios point elsewhere:
**Pick by what you're building:**
- **Content-heavy site** (blog, docs, marketing, e-commerce catalog): **Astro**. Ships almost no JS by default, and you can drop in React/Svelte/Vue components as islands where you need interactivity. Using a full app framework for this is overkill.
- **Dashboard / internal tool / app behind a login**: **Vite + React + React Router**. You don't need SSR, and skipping Next.js avoids a lot of complexity around server components, caching, and deployment.
- **Public app that needs SEO and fast first loads**: **Next.js** or **Nuxt** (Vue). Both are mature and have good hosting stories.
- **Small team, you value DX and speed of writing code**: **SvelteKit**. Less boilerplate, genuinely pleasant, smaller bundles. Trade-off is a thinner ecosystem — you'll occasionally write your own wrapper for something React has three options for.
- **Large team, enterprise, long-lived codebase**: **Angular**. Modern Angular (signals, standalone components) is much better than its old reputation suggests, and its opinionated structure and batteries-included tooling are real advantages when 30 people touch the same repo.
- **Web + mobile from one skillset**: **React**, so you can reuse knowledge with React Native.
**Two things that matter more than the framework choice:**
1. **Your rendering strategy.** SPA vs. SSR vs. static generation affects your architecture, hosting cost, and debugging experience far more than React vs. Vue does. Decide this deliberately rather than inheriting it from a framework's defaults.
2. **What you or your team already know.** Familiarity with a "worse" framework beats learning a "better" one on a real deadline. Frameworks converge on the same ideas anyway — components, reactive state, file-based routing.
**Worth avoiding:** starting with Solid or Qwik unless you specifically want their architectural properties and are comfortable being an early adopter. They're technically impressive but you'll hit gaps.
One caveat: my information has a cutoff, so check current versions and release notes before committing — Next.js in particular moves fast and has had some rough migrations. The broad landscape above has been stable for a while, though.
What are you building? I can give a more specific recommendation.

End of response · 21 lines · 2,540 characters · sha256 057de516069fc6339504c9da48cad67d9680163ade9bbb86c6915c55e0965da4

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-17 09:00:21 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
4 added, 0 dropped
Baseline
6 prior days with data; 1 matched the baseline value (2026-09-16)
Responses
before 2026-09-16 09:24:30 UTC, run 20260916T090004Z-fdcf7b; after 2026-09-17 09:24:55 UTC, run 20260917T090022Z-136fc3
Detected
2026-09-17 · run 20260917T090022Z-136fc3, started 2026-09-17 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-17/P26/anthropic/claude-opus-5/pick_change/picks/
Event ID
2026-09-17:P26:anthropic/claude-opus-5:pick_change:picks

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.