MODELDRIFT.WATCH

Sep 29 · Day 20

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

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

Short answer: default to React with Vite unless one of the cases below applies — then take the alternative, because the alternatives are genuinely better for their niches.

Content-heavy site (marketing, blog, docs, e-commerce storefront): Astro. It ships almost no JS by default, and you can drop React/Vue/Svelte components into individual islands where you need interactivity. For this category it's not a close call.

App behind a login (dashboards, internal tools, SaaS): Vite + React + TanStack Router + TanStack Query. No SSR complexity you don't need, fast builds, type-safe routing. A lot of people reach for Next.js here and then spend their time fighting caching semantics and server/client boundaries for SEO benefits that don't matter on an authenticated page.

Needs both SEO and real interactivity: Next.js (biggest ecosystem, most tutorials, most hiring pool) or SvelteKit (noticeably nicer to write, smaller bundles, smaller ecosystem). Nuxt if your team already likes Vue.

Large team, long-lived enterprise codebase: Angular is a defensible choice. Strong conventions and batteries included mean less bikeshedding across many developers, which matters more than raw ergonomics at that scale.

Mostly server-rendered with sprinkles of interactivity, and you have a backend in Rails/Django/Laravel/Go: consider skipping the JS framework. htmx or Alpine on top of server templates will get you there with a fraction of the machinery.

Two things worth saying plainly:

The choice matters less than it feels like it does. What your team already knows beats any framework's technical edge. If three people on your team are fluent in Vue, use Vue — the productivity difference swamps the framework difference.

Also, my sense of the ecosystem has a knowledge cutoff, and this area moves. The broad strokes above are stable, but check current status before committing — particularly the React meta-framework situation, which has been in flux (Remix merging into React Router, TanStack Start maturing, Next's App Router still settling).

If you tell me what you're building, team size, and what you already know, I can give you a single answer instead of a decision tree.

SEP 29afterPermalink

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.

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

Before baseline

2026-09-28 permalink

Scored
answered
Received
2026-09-28 09:22:39 UTC
Run
20260928T090007Z-07d4be
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,226 characters · 1,673 tokens out incl. hidden reasoning · 26.9 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Vite + React + TanStack Router + TanStack Query
  3. Next.js
  4. Angular
  5. htmx

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

Short answer: default to React with Vite unless one of the cases below applies — then take the alternative, because the alternatives are genuinely better for their niches.
**Content-heavy site** (marketing, blog, docs, e-commerce storefront): **Astro**. It ships almost no JS by default, and you can drop React/Vue/Svelte components into individual islands where you need interactivity. For this category it's not a close call.
**App behind a login** (dashboards, internal tools, SaaS): **Vite + React + TanStack Router + TanStack Query**. No SSR complexity you don't need, fast builds, type-safe routing. A lot of people reach for Next.js here and then spend their time fighting caching semantics and server/client boundaries for SEO benefits that don't matter on an authenticated page.
**Needs both SEO and real interactivity**: **Next.js** (biggest ecosystem, most tutorials, most hiring pool) or **SvelteKit** (noticeably nicer to write, smaller bundles, smaller ecosystem). Nuxt if your team already likes Vue.
**Large team, long-lived enterprise codebase**: **Angular** is a defensible choice. Strong conventions and batteries included mean less bikeshedding across many developers, which matters more than raw ergonomics at that scale.
**Mostly server-rendered with sprinkles of interactivity**, and you have a backend in Rails/Django/Laravel/Go: consider skipping the JS framework. **htmx** or Alpine on top of server templates will get you there with a fraction of the machinery.
Two things worth saying plainly:
The choice matters less than it feels like it does. What your team already knows beats any framework's technical edge. If three people on your team are fluent in Vue, use Vue — the productivity difference swamps the framework difference.
Also, my sense of the ecosystem has a knowledge cutoff, and this area moves. The broad strokes above are stable, but check current status before committing — particularly the React meta-framework situation, which has been in flux (Remix merging into React Router, TanStack Start maturing, Next's App Router still settling).
If you tell me what you're building, team size, and what you already know, I can give you a single answer instead of a decision tree.

End of response · 19 lines · 2,226 characters · sha256 46a3a20f478535b4d93aac6917bd6840b426afb522e859ae14bd9abd21faa16e

After this run

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

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-29 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; 2 matched the baseline value (2026-09-27, 2026-09-28)
Responses
before 2026-09-28 09:22:39 UTC, run 20260928T090007Z-07d4be; after 2026-09-29 09:23:43 UTC, run 20260929T090007Z-334891
Detected
2026-09-29 · run 20260929T090007Z-334891, started 2026-09-29 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-29/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-09-29: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.