MODELDRIFT.WATCH

Sep 21 · Day 12

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

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.

SEP 21afterPermalink

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.

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

Before baseline

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

After this run

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

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-21 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
6 prior days with data; 4 matched the baseline value (2026-09-14, 2026-09-15, 2026-09-16, 2026-09-17)
Responses
before 2026-09-17 09:24:55 UTC, run 20260917T090022Z-136fc3; after 2026-09-21 09:25:21 UTC, run 20260921T090021Z-989a7c
Detected
2026-09-21 · run 20260921T090021Z-989a7c, started 2026-09-21 09:00:21 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-21/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-21: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.