MODELDRIFT.WATCH

Sep 25 · Day 16

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 21beforePermalink

Picks read from the answer, in order
  1. Astro
  2. Svelte + SvelteKit
  3. Angular
  4. Middle ground between React and Svelte

Short answer: React with a meta-framework is the safest default, but it's genuinely not the best pick for every project. Here's how I'd actually decide.

Default choice: React + a meta-framework
Largest ecosystem, most third-party components, easiest hiring, most Stack Overflow/LLM training data when you get stuck. For the meta-framework: Next.js if you want the most-traveled path, React Router (v7, formerly Remix) if you want something simpler and less coupled to a hosting vendor, or TanStack Start if you like that ecosystem. The main cost is complexity — React Server Components and the client/server boundary confuse experienced developers, not just beginners.

Pick something else if:

  • •Content-heavy site (blog, docs, marketing) → Astro. Ships almost no JS by default and lets you drop in React/Vue/Svelte components for the interactive bits. Clearly the right tool here.
  • •You want the nicest development experience → Svelte + SvelteKit. Less boilerplate, great docs, genuinely enjoyable. Svelte 5's "runes" reworked the reactivity model, so older tutorials may not match. Smaller ecosystem and hiring pool.
  • •Large team, long-lived enterprise app → Angular. Much better than its reputation now (signals, standalone components), and its strong conventions are an asset when 30 people touch the same codebase.
  • •You already have a backend (Rails, Django, Laravel, Phoenix) → consider not adding an SPA framework at all. Server-rendered HTML plus HTMX or Alpine.js handles a surprising amount, and you skip the whole API-layer tax.
  • •Middle ground between React and Svelte → Vue + Nuxt. Excellent docs, stable, less churn than React, healthy ecosystem — just fewer jobs and niche libraries in the US market.

Mostly settled regardless of choice: use Vite for tooling, TypeScript, and pnpm or Bun. Those are close to consensus now.

One caveat: this ecosystem moves fast and my knowledge has a cutoff, so check current release notes before committing — especially for Svelte, Solid, and anything Server Components related.

If you tell me what you're building, who's building it, and whether you need SEO or offline support, I can narrow this to one recommendation instead of six.

SEP 25afterPermalink

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

Short answer: React + Vite if you want the safest bet, or SvelteKit / Nuxt if you're a small team optimizing for how fast and pleasant the work actually is.

Longer answer, because the right pick genuinely depends on a few things:

By project type

  • •Content-heavy site (marketing, docs, blog, e-commerce catalog) → Astro. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
  • •SPA / internal dashboard / behind a login → Vite + React (or Vue, or Svelte). You don't need a meta-framework. SEO doesn't matter, so skip the SSR complexity entirely. This is the most underrated option — a lot of people reach for Next.js and inherit a pile of server/client boundary problems they never needed.
  • •Public-facing app that needs SSR and SEO → Next.js (React), Nuxt (Vue), or SvelteKit (Svelte). All three are solid. Next.js has the biggest ecosystem and the most churn; Nuxt and SvelteKit are calmer.
  • •Large enterprise team, want strong conventions → Angular. Its reputation lags its current state — signals and standalone components modernized it substantially. Batteries-included, opinionated, good when you have many developers who need guardrails.

Tiebreakers

  • •Hiring, contractors, or needing Stack Overflow answers to exist → React. It's not the best framework, it's the one with the deepest gravity well.
  • •Small team, you control the stack, you value DX → Svelte 5 or Vue 3. Both have meaningfully less ceremony than React. Svelte's runes and Vue's composition API are, in my view, nicer reactivity models than hooks.
  • •Team already knows one of these → use that. This dominates almost every other consideration. Framework choice is rarely the thing that sinks a project.

What I'd want to know to be more useful: Is it public or behind auth? Solo or team? Do you need SEO? Where are you deploying (Vercel/Cloudflare/your own box)? Any existing stack to fit into?

One caveat: my knowledge has a cutoff, and this ecosystem moves fast — there may be newer releases or shifts I'm not aware of. The structural advice above should hold up, but check current versions and release notes before committing.

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

Before baseline

2026-09-21 permalink

Scored
answered
Received
2026-09-21 09:25:21 UTC
Run
20260921T090021Z-989a7c
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,246 characters · 1,824 tokens out incl. hidden reasoning · 26.7 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Svelte + SvelteKit
  3. Angular
  4. Middle ground between React and Svelte

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, but it's genuinely not the best pick for every project. Here's how I'd actually decide.
**Default choice: React + a meta-framework**
Largest ecosystem, most third-party components, easiest hiring, most Stack Overflow/LLM training data when you get stuck. For the meta-framework: Next.js if you want the most-traveled path, React Router (v7, formerly Remix) if you want something simpler and less coupled to a hosting vendor, or TanStack Start if you like that ecosystem. The main cost is complexity — React Server Components and the client/server boundary confuse experienced developers, not just beginners.
**Pick something else if:**
- **Content-heavy site** (blog, docs, marketing) → **Astro**. Ships almost no JS by default and lets you drop in React/Vue/Svelte components for the interactive bits. Clearly the right tool here.
- **You want the nicest development experience** → **Svelte + SvelteKit**. Less boilerplate, great docs, genuinely enjoyable. Svelte 5's "runes" reworked the reactivity model, so older tutorials may not match. Smaller ecosystem and hiring pool.
- **Large team, long-lived enterprise app** → **Angular**. Much better than its reputation now (signals, standalone components), and its strong conventions are an asset when 30 people touch the same codebase.
- **You already have a backend** (Rails, Django, Laravel, Phoenix) → consider not adding an SPA framework at all. Server-rendered HTML plus HTMX or Alpine.js handles a surprising amount, and you skip the whole API-layer tax.
- **Middle ground between React and Svelte** → **Vue + Nuxt**. Excellent docs, stable, less churn than React, healthy ecosystem — just fewer jobs and niche libraries in the US market.
**Mostly settled regardless of choice:** use Vite for tooling, TypeScript, and pnpm or Bun. Those are close to consensus now.
**One caveat:** this ecosystem moves fast and my knowledge has a cutoff, so check current release notes before committing — especially for Svelte, Solid, and anything Server Components related.
If you tell me what you're building, who's building it, and whether you need SEO or offline support, I can narrow this to one recommendation instead of six.

End of response · 18 lines · 2,246 characters · sha256 72b63d133379976d4233e642c24bea52acc6ccdda6da20e89b5e5d1c3839ed6e

After this run

2026-09-25 permalink

Scored
answered
Received
2026-09-25 09:23:04 UTC
Run
20260925T090007Z-f08d1f
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,247 characters · 1,974 tokens out incl. hidden reasoning · 30.2 s
Extracted picks, in order · confidence medium
  1. React + Vite
  2. Astro
  3. Next.js
  4. Angular
  5. Tiebreakers

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

Short answer: **React + Vite** if you want the safest bet, or **SvelteKit / Nuxt** if you're a small team optimizing for how fast and pleasant the work actually is.
Longer answer, because the right pick genuinely depends on a few things:
**By project type**
- **Content-heavy site** (marketing, docs, blog, e-commerce catalog) → **Astro**. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
- **SPA / internal dashboard / behind a login** → **Vite + React** (or Vue, or Svelte). You don't need a meta-framework. SEO doesn't matter, so skip the SSR complexity entirely. This is the most underrated option — a lot of people reach for Next.js and inherit a pile of server/client boundary problems they never needed.
- **Public-facing app that needs SSR and SEO** → **Next.js** (React), **Nuxt** (Vue), or **SvelteKit** (Svelte). All three are solid. Next.js has the biggest ecosystem and the most churn; Nuxt and SvelteKit are calmer.
- **Large enterprise team, want strong conventions** → **Angular**. Its reputation lags its current state — signals and standalone components modernized it substantially. Batteries-included, opinionated, good when you have many developers who need guardrails.
**Tiebreakers**
- *Hiring, contractors, or needing Stack Overflow answers to exist* → React. It's not the best framework, it's the one with the deepest gravity well.
- *Small team, you control the stack, you value DX* → Svelte 5 or Vue 3. Both have meaningfully less ceremony than React. Svelte's runes and Vue's composition API are, in my view, nicer reactivity models than hooks.
- *Team already knows one of these* → use that. This dominates almost every other consideration. Framework choice is rarely the thing that sinks a project.
**What I'd want to know to be more useful:** Is it public or behind auth? Solo or team? Do you need SEO? Where are you deploying (Vercel/Cloudflare/your own box)? Any existing stack to fit into?
One caveat: my knowledge has a cutoff, and this ecosystem moves fast — there may be newer releases or shifts I'm not aware of. The structural advice above should hold up, but check current versions and release notes before committing.

End of response · 20 lines · 2,247 characters · sha256 773666947628f31109a14221eafe185ed953336dee0b8bf97eb319f8d500d4e5

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-25 09:00:06 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
4 prior days with data; 2 matched the baseline value (2026-09-18, 2026-09-21)
Responses
before 2026-09-21 09:25:21 UTC, run 20260921T090021Z-989a7c; after 2026-09-25 09:23:04 UTC, run 20260925T090007Z-f08d1f
Detected
2026-09-25 · run 20260925T090007Z-f08d1f, started 2026-09-25 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-25/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-25: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.