MODELDRIFT.WATCH

Sep 30 · Day 21

MINOR · CLAUDE · QUESTION 31

Claude went back to its earlier list for a question about which JavaScript framework to start with.

Why it’s minor

The change lasted one day before the model went back.

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 29the changePermalink

Picks read from the answer, in order
  1. React + Vite
  2. Astro
  3. SvelteKit
  4. Angular

Short answer: React + Vite (or Next.js) if you care most about ecosystem and hiring; SvelteKit or Nuxt if you care most about developer experience; Astro if you're building something content-heavy.

The longer answer depends on what you're building:

Content-driven sites (blog, docs, marketing, e-commerce storefront) → Astro. It ships zero JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them. It's the clearest win in the current landscape for this category.

Full-stack app, want the safest long-term bet → React. It's still the largest ecosystem by a wide margin, which matters for hiring, third-party libraries, and finding answers to obscure problems. The open question is which router/meta-framework: Next.js is the default and best-supported, but Server Components add real conceptual overhead. If you don't need SSR-heavy features, React + Vite + TanStack Router is much simpler and stays out of your way. React Router v7 (the former Remix) is a good middle ground.

Full-stack app, optimizing for how pleasant it is to build → SvelteKit or Nuxt. Both are more internally coherent than the React ecosystem — routing, data loading, and forms feel like parts of one design rather than assembled pieces. Svelte 5's runes give you fine-grained reactivity with less ceremony than hooks. Nuxt is the more mature/enterprise-friendly of the two. The tradeoff is a smaller ecosystem, so you'll occasionally build something yourself that you'd have installed in React.

Large team, long-lived enterprise app → Angular is worth a real look. Signals, standalone components, and the newer template syntax fixed most of the historical complaints, and its opinionated structure genuinely helps when 30 developers touch the same codebase over five years.

Mostly server-rendered app needing sprinkles of interactivity → consider skipping frameworks. htmx, Alpine, or plain web components may be all you need, and you'll avoid a build pipeline you have to maintain.

A few things worth keeping in mind:

  • •The meta-framework choice now matters more than the view library. Next vs. SvelteKit vs. Nuxt shapes your daily work far more than React vs. Svelte vs. Vue does.
  • •Vite is the common substrate under nearly everything except Next. That's a point in favor of the Vite-based options for portability.
  • •Solid is technically excellent and pioneered a lot of what others adopted, but the ecosystem is small enough that I'd only pick it if you're comfortable filling gaps yourself.

If you tell me what you're building — team size, SEO needs, whether it's an internal tool or public product, how much interactivity — I can give you a more specific recommendation.

One caveat: this space moves quickly, and my information has a cutoff. Version numbers and project statuses are worth verifying before you commit.

SEP 30backPermalink

Picks read from the answer, in order
  1. Astro
  2. Next.js
  3. Vite + React + TanStack Router + TanStack Query
  4. Angular
  5. Svelte 5 + SvelteKit

Short answer: if you have no strong constraints, React + Next.js is the safest default — biggest ecosystem, most hiring options, most tutorials and AI-assistance trained on it. But "safest" isn't always "best," so here's how I'd actually decide:

By project type

Content-heavy site (blog, docs, marketing, e-commerce catalog) → Astro. Ships almost no JS by default, great SEO, and you can drop React/Vue/Svelte components into individual "islands" where you need interactivity.

Full-stack app that needs SEO or fast first load → Next.js (React), Nuxt (Vue), or SvelteKit. All three are mature. Pick based on which language model you enjoy more.

Dashboard or internal tool behind a login (SEO irrelevant) → skip the meta-framework overhead. Vite + React + TanStack Router + TanStack Query is a fantastic, boring, fast stack. SvelteKit in SPA mode is also great here.

Large team, long-lived enterprise app, heavy TypeScript → Angular is genuinely worth reconsidering. Signals and standalone components modernized it a lot, and its opinionated structure prevents the 12-different-patterns problem big teams get with React.

You want to enjoy writing code → Svelte 5 + SvelteKit. Least boilerplate, very clean reactivity model with runes, consistently tops developer-satisfaction surveys. Tradeoff: smaller ecosystem and fewer job listings.

Honest notes on the tradeoffs

  • •React's complexity has grown. Server Components, the client/server boundary, and caching semantics in Next.js are real learning costs. If you're solo and building a CRUD app, you may be paying for power you don't need.
  • •Vue/Nuxt is the underrated middle. Gentler curve than React, better docs than almost anyone, ecosystem large enough that you won't hit walls.
  • •Don't pick something with churn risk unless you enjoy that. Remix/React Router has had significant direction changes; TanStack Start is promising but newer. Fine for a side project, riskier for a client deliverable.

The thing that actually matters

Framework choice is one of the least consequential decisions in a new project. Your database schema, auth approach, and deployment story will cause you far more pain. Any of the options above will work fine for 95% of projects — so pick the one you or your team already know, and spend the saved decision energy elsewhere.

One caveat: my information has a cutoff date, and this ecosystem moves fast. Before committing, check current release status and recent activity for whichever one you pick — especially for the newer options.

What are you building? I can give a much more specific recommendation with that context.

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

Deviation the day it changed

2026-09-29 permalink

Scored
answered
Received
2026-09-29 09:23:43 UTC
Run
20260929T090007Z-334891
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,909 characters · 2,127 tokens out incl. hidden reasoning · 32.6 s
Extracted picks, in order · confidence medium
  1. React + Vite
  2. Astro
  3. SvelteKit
  4. Angular

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

Short answer: **React + Vite (or Next.js) if you care most about ecosystem and hiring; SvelteKit or Nuxt if you care most about developer experience; Astro if you're building something content-heavy.**
The longer answer depends on what you're building:
**Content-driven sites** (blog, docs, marketing, e-commerce storefront) → **Astro**. It ships zero JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them. It's the clearest win in the current landscape for this category.
**Full-stack app, want the safest long-term bet** → **React**. It's still the largest ecosystem by a wide margin, which matters for hiring, third-party libraries, and finding answers to obscure problems. The open question is which router/meta-framework: Next.js is the default and best-supported, but Server Components add real conceptual overhead. If you don't need SSR-heavy features, React + Vite + TanStack Router is much simpler and stays out of your way. React Router v7 (the former Remix) is a good middle ground.
**Full-stack app, optimizing for how pleasant it is to build** → **SvelteKit** or **Nuxt**. Both are more internally coherent than the React ecosystem — routing, data loading, and forms feel like parts of one design rather than assembled pieces. Svelte 5's runes give you fine-grained reactivity with less ceremony than hooks. Nuxt is the more mature/enterprise-friendly of the two. The tradeoff is a smaller ecosystem, so you'll occasionally build something yourself that you'd have installed in React.
**Large team, long-lived enterprise app** → **Angular** is worth a real look. Signals, standalone components, and the newer template syntax fixed most of the historical complaints, and its opinionated structure genuinely helps when 30 developers touch the same codebase over five years.
**Mostly server-rendered app needing sprinkles of interactivity** → consider skipping frameworks. htmx, Alpine, or plain web components may be all you need, and you'll avoid a build pipeline you have to maintain.
A few things worth keeping in mind:
- The meta-framework choice now matters more than the view library. Next vs. SvelteKit vs. Nuxt shapes your daily work far more than React vs. Svelte vs. Vue does.
- Vite is the common substrate under nearly everything except Next. That's a point in favor of the Vite-based options for portability.
- Solid is technically excellent and pioneered a lot of what others adopted, but the ecosystem is small enough that I'd only pick it if you're comfortable filling gaps yourself.
If you tell me what you're building — team size, SEO needs, whether it's an internal tool or public product, how much interactivity — I can give you a more specific recommendation.
One caveat: this space moves quickly, and my information has a cutoff. Version numbers and project statuses are worth verifying before you commit.

End of response · 23 lines · 2,909 characters · sha256 f524e665616cc3b0bc299cf339ba50c4cd8db7f39d45c3a5d70f90eca0d25369

Reverted back to baseline

2026-09-30 permalink

Scored
answered
Received
2026-09-30 09:21:47 UTC
Run
20260930T090007Z-45ce12
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,686 characters · 1,924 tokens out incl. hidden reasoning · 27.1 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Next.js
  3. Vite + React + TanStack Router + TanStack Query
  4. Angular
  5. Svelte 5 + SvelteKit

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

Short answer: **if you have no strong constraints, React + Next.js is the safest default** — biggest ecosystem, most hiring options, most tutorials and AI-assistance trained on it. But "safest" isn't always "best," so here's how I'd actually decide:
## By project type
**Content-heavy site** (blog, docs, marketing, e-commerce catalog) → **Astro**. Ships almost no JS by default, great SEO, and you can drop React/Vue/Svelte components into individual "islands" where you need interactivity.
**Full-stack app that needs SEO or fast first load** → **Next.js** (React), **Nuxt** (Vue), or **SvelteKit**. All three are mature. Pick based on which language model you enjoy more.
**Dashboard or internal tool behind a login** (SEO irrelevant) → skip the meta-framework overhead. **Vite + React + TanStack Router + TanStack Query** is a fantastic, boring, fast stack. SvelteKit in SPA mode is also great here.
**Large team, long-lived enterprise app, heavy TypeScript** → **Angular** is genuinely worth reconsidering. Signals and standalone components modernized it a lot, and its opinionated structure prevents the 12-different-patterns problem big teams get with React.
**You want to enjoy writing code** → **Svelte 5 + SvelteKit**. Least boilerplate, very clean reactivity model with runes, consistently tops developer-satisfaction surveys. Tradeoff: smaller ecosystem and fewer job listings.
## Honest notes on the tradeoffs
- **React's complexity has grown.** Server Components, the client/server boundary, and caching semantics in Next.js are real learning costs. If you're solo and building a CRUD app, you may be paying for power you don't need.
- **Vue/Nuxt is the underrated middle.** Gentler curve than React, better docs than almost anyone, ecosystem large enough that you won't hit walls.
- **Don't pick something with churn risk** unless you enjoy that. Remix/React Router has had significant direction changes; TanStack Start is promising but newer. Fine for a side project, riskier for a client deliverable.
## The thing that actually matters
Framework choice is one of the *least* consequential decisions in a new project. Your database schema, auth approach, and deployment story will cause you far more pain. Any of the options above will work fine for 95% of projects — so pick the one you or your team already know, and spend the saved decision energy elsewhere.
One caveat: my information has a cutoff date, and this ecosystem moves fast. Before committing, check current release status and recent activity for whichever one you pick — especially for the newer options.
What are you building? I can give a much more specific recommendation with that context.

End of response · 27 lines · 2,686 characters · sha256 77f397f2de00da2d6610cc1a898d4ba87efa2f5cf302bd77909bd21b3210611c

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-30 09:00:07 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; 3 matched the baseline value (2026-09-27, 2026-09-28, 2026-09-29)
Responses
deviation 2026-09-29 09:23:43 UTC, run 20260929T090007Z-334891; reverted 2026-09-30 09:21:47 UTC, run 20260930T090007Z-45ce12
Detected
2026-09-30 · run 20260930T090007Z-45ce12, started 2026-09-30 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-30/P26/anthropic/claude-opus-5/transient_anomaly/picks.top/
Event ID
2026-09-30:P26:anthropic/claude-opus-5:transient_anomaly: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.