MODELDRIFT.WATCH

Sep 20 · Day 11

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 20afterPermalink

Picks read from the answer, in order
  1. Hiring
  2. SvelteKit
  3. Vue 3 + Nuxt
  4. Angular
  5. Astro

Short answer: if you have no strong constraints, React with a meta-framework is still the safest default, but it's probably not the best choice for most small projects. Here's how I'd actually decide:

Pick based on your main constraint

Hiring, ecosystem size, or "will this be maintainable by whoever comes next" → React. It has the largest library ecosystem and talent pool by a wide margin. For the meta-framework: Next.js is the default, but if Server Components feel like more complexity than you need, look at TanStack Start or React Router v7 (formerly Remix) for a more conventional model.

Velocity for a small team or solo dev → SvelteKit. Least boilerplate of anything mature, excellent full-stack story, genuinely pleasant to write. Svelte 5's runes changed the reactivity model, so make sure tutorials you follow are current. Smaller ecosystem is the real tradeoff — you'll occasionally write a wrapper yourself.

Balanced middle ground → Vue 3 + Nuxt. Great docs, ergonomic Composition API, ecosystem large enough that you rarely hit gaps. Very strong choice that people underrate because it's not trendy.

Large team, enterprise, lots of structure needed → Angular. Batteries-included, opinionated, and much better than its reputation since standalone components and signals landed. Prevents a lot of architectural bikeshedding.

Content-heavy site, blog, docs, marketing → Astro. Ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity.

Mostly server-rendered CRUD with light interactivity → consider no framework. HTMX or Alpine.js on top of whatever backend you like is a legitimate answer, and a lot of projects reach for a SPA framework they don't need.

My actual default

For a new app with no constraints, I'd start with SvelteKit. The productivity difference is real, and the framework does more for you with less ceremony. If there's any chance you'll need to hire, or you depend on a niche library that only has a React binding, go React + TanStack Start instead.

One caveat: this ecosystem moves fast and my information has a cutoff, so check the current state of Svelte 5 adoption and whatever the React community's consensus on RSC is before committing. Also worth weighing above everything else — if your team already knows one of these well, that familiarity usually beats any technical edge on this list.

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-20 permalink

Scored
answered
Received
2026-09-20 09:23:41 UTC
Run
20260920T090019Z-bbedf3
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,472 characters · 1,724 tokens out incl. hidden reasoning · 27.0 s
Extracted picks, in order · confidence medium
  1. Hiring
  2. SvelteKit
  3. Vue 3 + Nuxt
  4. Angular
  5. Astro

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

Short answer: if you have no strong constraints, **React with a meta-framework** is still the safest default, but it's probably not the *best* choice for most small projects. Here's how I'd actually decide:
## Pick based on your main constraint
**Hiring, ecosystem size, or "will this be maintainable by whoever comes next"** → **React**. It has the largest library ecosystem and talent pool by a wide margin. For the meta-framework: Next.js is the default, but if Server Components feel like more complexity than you need, look at **TanStack Start** or **React Router v7** (formerly Remix) for a more conventional model.
**Velocity for a small team or solo dev** → **SvelteKit**. Least boilerplate of anything mature, excellent full-stack story, genuinely pleasant to write. Svelte 5's runes changed the reactivity model, so make sure tutorials you follow are current. Smaller ecosystem is the real tradeoff — you'll occasionally write a wrapper yourself.
**Balanced middle ground** → **Vue 3 + Nuxt**. Great docs, ergonomic Composition API, ecosystem large enough that you rarely hit gaps. Very strong choice that people underrate because it's not trendy.
**Large team, enterprise, lots of structure needed** → **Angular**. Batteries-included, opinionated, and much better than its reputation since standalone components and signals landed. Prevents a lot of architectural bikeshedding.
**Content-heavy site, blog, docs, marketing** → **Astro**. Ships almost no JS by default and lets you drop in React/Vue/Svelte components only where you need interactivity.
**Mostly server-rendered CRUD with light interactivity** → consider **no framework**. HTMX or Alpine.js on top of whatever backend you like is a legitimate answer, and a lot of projects reach for a SPA framework they don't need.
## My actual default
For a new app with no constraints, I'd start with **SvelteKit**. The productivity difference is real, and the framework does more for you with less ceremony. If there's any chance you'll need to hire, or you depend on a niche library that only has a React binding, go **React + TanStack Start** instead.
One caveat: this ecosystem moves fast and my information has a cutoff, so check the current state of Svelte 5 adoption and whatever the React community's consensus on RSC is before committing. Also worth weighing above everything else — if your team already knows one of these well, that familiarity usually beats any technical edge on this list.

End of response · 21 lines · 2,472 characters · sha256 53c9c73a0a5ba59dd153b493883b8d73224cad7b136ff09c102235f50745a45f

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-20 09:00:19 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
5 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-20 09:23:41 UTC, run 20260920T090019Z-bbedf3
Detected
2026-09-20 · run 20260920T090019Z-bbedf3, started 2026-09-20 09:00:19 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-20/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-20: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.