MODELDRIFT.WATCH

Oct 2 · Day 23

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?

OCT 1beforePermalink

Picks read from the answer, in order
  1. Astro
  2. Vite + React
  3. Next.js
  4. React + Expo/React Native
  5. Angular

Short answer: if you have no strong constraints, React with a meta-framework is the safest default — biggest ecosystem, most hiring and tutorial mass, and the thing most tooling assumes. But the honest answer depends on what you're building, and for several common cases I'd pick something else.

By project type:

  • •Content-heavy site (blog, docs, marketing): Astro. Ships almost no JS by default, and you can drop in React/Svelte components for the interactive bits.
  • •Internal tool / dashboard / app behind a login: Vite + React (or Vue/Svelte) as a plain SPA, with TanStack Query and TanStack Router. You don't need SSR, and skipping it removes a lot of complexity.
  • •Full-stack product needing SEO, auth, and data loading: Next.js, Nuxt (Vue), or SvelteKit. All three are good. Next has the largest ecosystem but also the most churn and the steepest conceptual load right now with Server Components. SvelteKit and Nuxt are noticeably more pleasant for small teams.
  • •You'll also need a mobile app: React + Expo/React Native. Code sharing is imperfect, but skill sharing is real.
  • •Large enterprise team, 5+ year lifespan, lots of turnover: Angular is a defensible choice. Batteries included, strong conventions, less bikeshedding. Or React with aggressively enforced conventions.
  • •Your backend is Rails/Django/Laravel/Phoenix and the app is mostly CRUD: consider not adopting a JS framework at all. Server-rendered HTML plus Hotwire/LiveView/HTMX is less machinery for the same result.

A couple of opinions worth flagging as opinions: React Server Components are powerful but genuinely add complexity, and plenty of experienced people think the current tradeoff isn't worth it for small-to-mid projects. If that worries you, React Router (v7) or TanStack Start give you React with less magic. And Svelte is the one I'd most often recommend for a small team shipping fast, with the real caveat that the ecosystem and hiring pool are much smaller.

What matters more than the choice: use TypeScript, use Vite (or whatever your framework wraps it in), follow your framework's conventions instead of inventing architecture, and don't add state management, a component library, and an ORM abstraction before you have a working page.

One caveat: this space moves fast and my information has a cutoff, so check current release status before committing — particularly for anything on a major version boundary.

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

OCT 2afterPermalink

Picks read from the answer, in order
  1. Picking React
  2. Picking SvelteKit
  3. Picking Nuxt
  4. Picking Astro
  5. Picking Angular

Short answer: React with a meta-framework (Next.js or React Router) if you care most about ecosystem and hiring; SvelteKit or Nuxt if you care most about developer experience. Both are defensible choices in 2025 and neither will be a regret.

More specifically, matched to situations:

Picking React (+ Next.js, React Router, or TanStack Start)
The pragmatic default. Largest library ecosystem, most component kits, most Stack Overflow answers, most AI-tooling familiarity, easiest hiring. Downside: it's currently the most conceptually complicated option — Server Components, the client/server boundary, and caching semantics trip up a lot of people. If you just want a client-rendered SPA, React Router or TanStack Start are simpler than Next.js and give you less framework opinion to fight.

Picking SvelteKit
If you value writing less code and a smaller mental model. Svelte 5's runes gave it a signals-based reactivity system that's genuinely pleasant, and SvelteKit's routing/data-loading story is cleaner than Next's. Tradeoff: fewer off-the-shelf components, smaller talent pool.

Picking Nuxt (Vue)
A good middle ground — strong ecosystem (though smaller than React's), excellent docs, more structure than Svelte without React's complexity. Especially worth considering if your team is in Europe or Asia where Vue hiring is easier.

Picking Astro
If the project is mostly content — marketing site, blog, docs, e-commerce storefront. It ships almost no JS by default and lets you drop in React/Svelte/Vue components only where you need interactivity. Wrong choice for an app-like dashboard.

Picking Angular
If you're a large team or enterprise that wants strong conventions, batteries-included tooling, and TypeScript-first everything. Modern Angular with signals and standalone components is much better than its reputation suggests.

Picking nothing
Worth saying out loud: if you're building a server-rendered app with modest interactivity, Rails/Django/Laravel/Phoenix plus a sprinkle of Alpine or HTMX will get you there faster than any of the above.

The factors that should actually drive your decision, roughly in order: what your team already knows, whether you need SEO/SSR, how much you depend on pre-built UI components, and expected app complexity. Framework performance differences are real but rarely the bottleneck in practice.

One caveat: this space moves fast and my information has a cutoff, so verify current versions and release status before committing.

If you tell me what you're building, team size, and what you've used before, I can give you a single concrete recommendation instead of a menu.

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

Before baseline

2026-10-01 permalink

Scored
answered
Received
2026-10-01 09:22:55 UTC
Run
20261001T090007Z-857bc9
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,575 characters · 2,067 tokens out incl. hidden reasoning · 29.3 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Vite + React
  3. Next.js
  4. React + Expo/React Native
  5. Angular

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 the safest default — biggest ecosystem, most hiring and tutorial mass, and the thing most tooling assumes. But the honest answer depends on what you're building, and for several common cases I'd pick something else.
**By project type:**
- **Content-heavy site** (blog, docs, marketing): **Astro**. Ships almost no JS by default, and you can drop in React/Svelte components for the interactive bits.
- **Internal tool / dashboard / app behind a login**: **Vite + React** (or Vue/Svelte) as a plain SPA, with TanStack Query and TanStack Router. You don't need SSR, and skipping it removes a lot of complexity.
- **Full-stack product needing SEO, auth, and data loading**: **Next.js**, **Nuxt** (Vue), or **SvelteKit**. All three are good. Next has the largest ecosystem but also the most churn and the steepest conceptual load right now with Server Components. SvelteKit and Nuxt are noticeably more pleasant for small teams.
- **You'll also need a mobile app**: **React + Expo/React Native**. Code sharing is imperfect, but skill sharing is real.
- **Large enterprise team, 5+ year lifespan, lots of turnover**: **Angular** is a defensible choice. Batteries included, strong conventions, less bikeshedding. Or React with aggressively enforced conventions.
- **Your backend is Rails/Django/Laravel/Phoenix and the app is mostly CRUD**: consider not adopting a JS framework at all. Server-rendered HTML plus Hotwire/LiveView/HTMX is less machinery for the same result.
**A couple of opinions worth flagging as opinions:** React Server Components are powerful but genuinely add complexity, and plenty of experienced people think the current tradeoff isn't worth it for small-to-mid projects. If that worries you, React Router (v7) or TanStack Start give you React with less magic. And Svelte is the one I'd most often recommend for a small team shipping fast, with the real caveat that the ecosystem and hiring pool are much smaller.
**What matters more than the choice:** use TypeScript, use Vite (or whatever your framework wraps it in), follow your framework's conventions instead of inventing architecture, and don't add state management, a component library, and an ORM abstraction before you have a working page.
One caveat: this space moves fast and my information has a cutoff, so check current release status before committing — particularly for anything on a major version boundary.
If you tell me what you're building, team size, and whether SEO matters, I can narrow it to one.

End of response · 18 lines · 2,575 characters · sha256 6a967b985a3ac68a02eb93ee0bff53d195c7ce6c0b6f808e1db610e78132a41a

After this run

2026-10-02 permalink

Scored
answered
Received
2026-10-02 09:22:54 UTC
Run
20261002T090008Z-e178a0
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,657 characters · 2,036 tokens out incl. hidden reasoning · 28.5 s
Extracted picks, in order · confidence medium
  1. Picking React
  2. Picking SvelteKit
  3. Picking Nuxt
  4. Picking Astro
  5. Picking Angular

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

Short answer: **React with a meta-framework (Next.js or React Router) if you care most about ecosystem and hiring; SvelteKit or Nuxt if you care most about developer experience.** Both are defensible choices in 2025 and neither will be a regret.
More specifically, matched to situations:
**Picking React (+ Next.js, React Router, or TanStack Start)**
The pragmatic default. Largest library ecosystem, most component kits, most Stack Overflow answers, most AI-tooling familiarity, easiest hiring. Downside: it's currently the most conceptually complicated option — Server Components, the client/server boundary, and caching semantics trip up a lot of people. If you just want a client-rendered SPA, React Router or TanStack Start are simpler than Next.js and give you less framework opinion to fight.
**Picking SvelteKit**
If you value writing less code and a smaller mental model. Svelte 5's runes gave it a signals-based reactivity system that's genuinely pleasant, and SvelteKit's routing/data-loading story is cleaner than Next's. Tradeoff: fewer off-the-shelf components, smaller talent pool.
**Picking Nuxt (Vue)**
A good middle ground — strong ecosystem (though smaller than React's), excellent docs, more structure than Svelte without React's complexity. Especially worth considering if your team is in Europe or Asia where Vue hiring is easier.
**Picking Astro**
If the project is mostly content — marketing site, blog, docs, e-commerce storefront. It ships almost no JS by default and lets you drop in React/Svelte/Vue components only where you need interactivity. Wrong choice for an app-like dashboard.
**Picking Angular**
If you're a large team or enterprise that wants strong conventions, batteries-included tooling, and TypeScript-first everything. Modern Angular with signals and standalone components is much better than its reputation suggests.
**Picking nothing**
Worth saying out loud: if you're building a server-rendered app with modest interactivity, Rails/Django/Laravel/Phoenix plus a sprinkle of Alpine or HTMX will get you there faster than any of the above.
The factors that should actually drive your decision, roughly in order: what your team already knows, whether you need SEO/SSR, how much you depend on pre-built UI components, and expected app complexity. Framework performance differences are real but rarely the bottleneck in practice.
One caveat: this space moves fast and my information has a cutoff, so verify current versions and release status before committing.
If you tell me what you're building, team size, and what you've used before, I can give you a single concrete recommendation instead of a menu.

End of response · 27 lines · 2,657 characters · sha256 80020847ded1b448045a7b1e62da2c4f6045ce24daef7df80a97570b5decad40

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-10-02 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
7 prior days with data; 4 matched the baseline value (2026-09-27, 2026-09-28, 2026-09-30, 2026-10-01)
Responses
before 2026-10-01 09:22:55 UTC, run 20261001T090007Z-857bc9; after 2026-10-02 09:22:54 UTC, run 20261002T090008Z-e178a0
Detected
2026-10-02 · run 20261002T090008Z-e178a0, started 2026-10-02 09:00:08 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-10-02/P26/anthropic/claude-opus-5/pick_change/picks.top/
Event ID
2026-10-02: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.