MODELDRIFT.WATCH

Sep 14 · Day 5

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

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.

SEP 14afterPermalink

Picks read from the answer, in order
  1. React with Vite
  2. Need SSR
  3. React Server Components
  4. Solid and Qwik

Short answer: React with Vite if you want the safest bet, or SvelteKit / Nuxt if you care most about developer happiness. But the right pick depends on a few things, so here's how I'd actually decide.

Quick decision guide

Building a marketing site, blog, docs, or anything content-heavy?
→ Astro. Ships almost no JS by default, great Markdown/MDX story, and you can drop in React/Vue/Svelte components for the interactive bits. It's the clear winner in this category and not really close.

Building an app behind a login (dashboard, SaaS tool, internal tool)?
→ React + Vite + React Router, or TanStack Router if you want best-in-class type-safe routing. You don't need a meta-framework for SEO if there's nothing to index. This stack is boring, fast to build with, and easy to hire for.

Need SSR, SEO, and app-like interactivity in one product?
→ Next.js if you're on React and want the default path (be aware the App Router + Server Components model has a real learning curve). Nuxt if you prefer Vue — it's arguably the most cohesive full-stack framework right now. SvelteKit if you want the least ceremony.

Large team, long-lived enterprise codebase, lots of devs cycling through?
→ Angular deserves a fresh look. Modern Angular (signals, standalone components) is a genuinely different and much better framework than the one people complain about. Its opinionated, batteries-included structure is an asset when you have 40 developers and high turnover.

Optimizing for your own enjoyment and speed on a small team?
→ SvelteKit. Svelte 5's runes made reactivity more explicit and predictable, and you write noticeably less code than the React equivalent. The tradeoff is a smaller ecosystem — you'll occasionally write a wrapper yourself instead of installing one.

A few honest caveats

  • •Ecosystem size is the one thing you can't easily fix later. React's gravitational pull means auth libraries, component kits, charting, drag-and-drop, and Stack Overflow answers all target it first. That matters more than any DX advantage when you hit an unusual requirement at 11pm.
  • •Don't pick based on benchmarks. The performance differences between these frameworks are dwarfed by your own architectural choices — how much data you ship, how many round trips you make, whether you lazy-load.
  • •React Server Components are the main thing to think hard about. They're powerful but they change the mental model significantly, and the ecosystem is still catching up. If that complexity isn't buying you something specific, a plain SPA or a simpler SSR framework is a legitimate choice, not a cop-out.
  • •Solid and Qwik are technically impressive but I'd only recommend them if you have a specific reason and tolerance for smaller communities.

One caveat: my knowledge has a cutoff, and this space moves fast. Version numbers and the state of newer tools like TanStack Start may have shifted, so worth sanity-checking current release status before you commit.

If you tell me what you're building, the team size, and whether SEO matters, I can narrow this to one recommendation.

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

Before baseline

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

After this run

2026-09-14 permalink

Scored
answered
Received
2026-09-14 09:27:28 UTC
Run
20260914T090022Z-e98262
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
3,157 characters · 2,172 tokens out incl. hidden reasoning · 32.2 s
Extracted picks, in order · confidence medium
  1. React with Vite
  2. Need SSR
  3. React Server Components
  4. Solid and Qwik

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

Short answer: **React with Vite** if you want the safest bet, or **SvelteKit / Nuxt** if you care most about developer happiness. But the right pick depends on a few things, so here's how I'd actually decide.
## Quick decision guide
**Building a marketing site, blog, docs, or anything content-heavy?**
→ **Astro.** Ships almost no JS by default, great Markdown/MDX story, and you can drop in React/Vue/Svelte components for the interactive bits. It's the clear winner in this category and not really close.
**Building an app behind a login (dashboard, SaaS tool, internal tool)?**
→ **React + Vite + React Router**, or **TanStack Router** if you want best-in-class type-safe routing. You don't need a meta-framework for SEO if there's nothing to index. This stack is boring, fast to build with, and easy to hire for.
**Need SSR, SEO, and app-like interactivity in one product?**
→ **Next.js** if you're on React and want the default path (be aware the App Router + Server Components model has a real learning curve). **Nuxt** if you prefer Vue — it's arguably the most cohesive full-stack framework right now. **SvelteKit** if you want the least ceremony.
**Large team, long-lived enterprise codebase, lots of devs cycling through?**
→ **Angular** deserves a fresh look. Modern Angular (signals, standalone components) is a genuinely different and much better framework than the one people complain about. Its opinionated, batteries-included structure is an asset when you have 40 developers and high turnover.
**Optimizing for your own enjoyment and speed on a small team?**
→ **SvelteKit.** Svelte 5's runes made reactivity more explicit and predictable, and you write noticeably less code than the React equivalent. The tradeoff is a smaller ecosystem — you'll occasionally write a wrapper yourself instead of installing one.
## A few honest caveats
- **Ecosystem size is the one thing you can't easily fix later.** React's gravitational pull means auth libraries, component kits, charting, drag-and-drop, and Stack Overflow answers all target it first. That matters more than any DX advantage when you hit an unusual requirement at 11pm.
- **Don't pick based on benchmarks.** The performance differences between these frameworks are dwarfed by your own architectural choices — how much data you ship, how many round trips you make, whether you lazy-load.
- **React Server Components are the main thing to think hard about.** They're powerful but they change the mental model significantly, and the ecosystem is still catching up. If that complexity isn't buying you something specific, a plain SPA or a simpler SSR framework is a legitimate choice, not a cop-out.
- **Solid and Qwik** are technically impressive but I'd only recommend them if you have a specific reason and tolerance for smaller communities.
One caveat: my knowledge has a cutoff, and this space moves fast. Version numbers and the state of newer tools like TanStack Start may have shifted, so worth sanity-checking current release status before you commit.
If you tell me what you're building, the team size, and whether SEO matters, I can narrow this to one recommendation.

End of response · 29 lines · 3,157 characters · sha256 b1b232a570382b7174d7c8e457971f0b9cff588758d34d8902014bf93a4d295a

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-14 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
first extracted pick differs from the baseline's (full lists below)
Baseline
3 prior days with data; 1 matched the baseline value (2026-09-12)
Responses
before 2026-09-12 09:23:14 UTC, run 20260912T090021Z-c0c86e; after 2026-09-14 09:27:28 UTC, run 20260914T090022Z-e98262
Detected
2026-09-14 · run 20260914T090022Z-e98262, started 2026-09-14 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-14/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-14: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.