MODELDRIFT.WATCH

Question 31 · Sep 28 · Day 19

Claude on Question 31, Sep 28

Which JavaScript framework should I start a new project with today?

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.

sha256 46a3a20f4785… · 24 tokens in · 1,673 out · 26.9 s · via Claude Platform on AWS · stopped on its own

Sep 28, the whole dayQuestion 31, every day

Exact recordShowHideThe model id, the run, the verbatim text with line numbers and its full sha256
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)
Date
2026-09-28 · run 20260928T090007Z-07d4be · scorer v1
Scored
answered
Changes
Minor Pick-list change: changed its list for a question about which JavaScript framework to start with
sha256
46a3a20f478535b4d93aac6917bd6840b426afb522e859ae14bd9abd21faa16e
Permalink
https://modeldrift.watch/r/2026-09-28/P26/anthropic/claude-opus-5/
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