MODELDRIFT.WATCH

Sep 28 · Day 19

MINOR · CLAUDE · QUESTION 31

Claude changed its list 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 27beforePermalink

Picks read from the answer, in order
  1. Astro
  2. Dashboard / SPA with no SEO needs
  3. Next.js
  4. SvelteKit
  5. Angular
  6. React
  7. Inertia.js

Short answer: if you have no strong constraints, React with Vite (add React Router if you need routing) or Next.js if you need server rendering. It's the safest default — biggest ecosystem, easiest hiring, most answers when you get stuck. But the "right" pick depends a lot on what you're building:

By use case

  • •Content-heavy site (blog, docs, marketing, e-commerce storefront): Astro. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
  • •Dashboard / SPA with no SEO needs: Vite + React (or Vue). Skip the meta-framework — you don't need server components or SSR complexity for an app behind a login.
  • •Full-stack app needing SSR, routing, data loading: Next.js, Nuxt (Vue), or SvelteKit. Next has the most resources and hosting support; Nuxt and SvelteKit are generally considered nicer to work with day to day.
  • •Best developer experience, small team: SvelteKit or Nuxt. Less boilerplate, less ceremony, genuinely pleasant. Trade-off is a smaller ecosystem and hiring pool.
  • •Large enterprise team, long-lived codebase: Angular. Opinionated and batteries-included, which is a feature when 40 people touch the code. It's improved a lot recently (signals, standalone components).
  • •Web + native mobile from one codebase: React (via React Native / Expo). This basically decides it for you.
  • •Adding interactivity to an existing Rails/Laravel/Django app: don't reach for a SPA framework. Use Inertia.js (with Vue or React), HTMX, or the framework's native tooling (Hotwire/Turbo, Livewire).

The honest meta-answer

Team familiarity beats framework quality almost every time. If you or your team already know one of these well, use that. All the major options are capable of building essentially any app; the differences show up in bundle size and ergonomics, not in what's possible.

The decision that actually matters more than framework choice is your rendering model — static, SSR, SPA, or a mix. Pick that based on SEO and performance needs first, then choose the framework that does it well.

Caveats

  • •My knowledge has a cutoff, and this space moves fast. Check current release notes before committing — versions and best practices may have shifted.
  • •Avoid picking something very new or niche (Qwik, Solid, etc.) for a project you need to maintain for years unless you specifically want their tradeoffs and can live with a thin ecosystem.

If you tell me what you're building, team size, and whether you need SEO or native mobile, I can narrow this to one recommendation.

SEP 28afterPermalink

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.

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

Before baseline

2026-09-27 permalink

Scored
answered
Received
2026-09-27 09:22:31 UTC
Run
20260927T090007Z-7adb14
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,654 characters · 1,850 tokens out incl. hidden reasoning · 27.7 s
Extracted picks, in order · confidence medium
  1. Astro
  2. Dashboard / SPA with no SEO needs
  3. Next.js
  4. SvelteKit
  5. Angular
  6. React
  7. Inertia.js

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

Short answer: **if you have no strong constraints, React with Vite (add React Router if you need routing) or Next.js if you need server rendering.** It's the safest default — biggest ecosystem, easiest hiring, most answers when you get stuck. But the "right" pick depends a lot on what you're building:
**By use case**
- **Content-heavy site** (blog, docs, marketing, e-commerce storefront): **Astro**. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
- **Dashboard / SPA with no SEO needs**: **Vite + React** (or Vue). Skip the meta-framework — you don't need server components or SSR complexity for an app behind a login.
- **Full-stack app needing SSR, routing, data loading**: **Next.js**, **Nuxt** (Vue), or **SvelteKit**. Next has the most resources and hosting support; Nuxt and SvelteKit are generally considered nicer to work with day to day.
- **Best developer experience, small team**: **SvelteKit** or **Nuxt**. Less boilerplate, less ceremony, genuinely pleasant. Trade-off is a smaller ecosystem and hiring pool.
- **Large enterprise team, long-lived codebase**: **Angular**. Opinionated and batteries-included, which is a feature when 40 people touch the code. It's improved a lot recently (signals, standalone components).
- **Web + native mobile from one codebase**: **React** (via React Native / Expo). This basically decides it for you.
- **Adding interactivity to an existing Rails/Laravel/Django app**: don't reach for a SPA framework. Use **Inertia.js** (with Vue or React), **HTMX**, or the framework's native tooling (Hotwire/Turbo, Livewire).
**The honest meta-answer**
Team familiarity beats framework quality almost every time. If you or your team already know one of these well, use that. All the major options are capable of building essentially any app; the differences show up in bundle size and ergonomics, not in what's possible.
The decision that actually matters more than framework choice is your **rendering model** — static, SSR, SPA, or a mix. Pick that based on SEO and performance needs first, then choose the framework that does it well.
**Caveats**
- My knowledge has a cutoff, and this space moves fast. Check current release notes before committing — versions and best practices may have shifted.
- Avoid picking something very new or niche (Qwik, Solid, etc.) for a project you need to maintain for years unless you specifically want their tradeoffs and can live with a thin ecosystem.
If you tell me what you're building, team size, and whether you need SEO or native mobile, I can narrow this to one recommendation.

End of response · 24 lines · 2,654 characters · sha256 b10aa9370f572e61fa432b49fa7ad53f621575dc4d1deb438db735f5f167bd57

After this run

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

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-28 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
1 added, 3 dropped
Baseline
5 prior days with data; 1 matched the baseline value (2026-09-27)
Responses
before 2026-09-27 09:22:31 UTC, run 20260927T090007Z-7adb14; after 2026-09-28 09:22:39 UTC, run 20260928T090007Z-07d4be
Detected
2026-09-28 · run 20260928T090007Z-07d4be, started 2026-09-28 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-28/P26/anthropic/claude-opus-5/pick_change/picks/
Event ID
2026-09-28:P26:anthropic/claude-opus-5:pick_change:picks

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.