Claude on Question 31, Sep 15

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

Default answer: React, via Next.js if you need server rendering, or Vite + React + TanStack Router if it's a pure client-side app.

Not because it's the most elegant — it isn't — but because the ecosystem gravity is overwhelming. Any library you need exists, any problem you hit has been Googled before, and you can hire for it. For most projects, that matters more than technical elegance.

That said, there are situations where something else is clearly better:

•Content-heavy site (marketing, docs, blog, mostly-static with some interactive bits) → Astro. Ships almost no JS by default, and you can drop React/Vue/Svelte components into islands where you actually need interactivity. Using Next.js for this is overkill.
•Small team, velocity matters, hiring isn't a constraint → SvelteKit or Nuxt. Both have materially better DX than Next. SvelteKit especially — less ceremony, smaller bundles, and the docs are excellent. The tradeoff is a thinner ecosystem of off-the-shelf components.
•Large org, multiple teams, long-lived codebase → Angular is a legitimate choice again. The signals-based rewrite modernized it considerably, and strong conventions plus batteries-included tooling reduce bikeshedding when you have 40 developers.
•You already have a server-rendered backend (Rails, Django, Laravel, Phoenix) → consider not adding a SPA framework at all. HTMX, Hotwire, or LiveView will get you most of the way with a fraction of the complexity.

Two honest caveats about the default recommendation. React's complexity has genuinely increased — Server Components and the Next.js App Router are powerful but have a real learning curve, and plenty of experienced developers find them frustrating. And Next.js has some coupling to Vercel's deployment model that's worth understanding before you commit. If neither appeals, SvelteKit is my second pick without much hesitation.

Things that will affect your outcome more than this decision: use TypeScript, pick what your team already knows if they know something, and check that your deployment target is well-supported before you're three months in.

One note — framework releases move fast and my information has a cutoff, so worth a quick sanity check on current versions.

What are you building? I can be more specific with a bit of context.

sha256 22d7721816ac… · 24 tokens in · 2,229 out · 35.1 s · via Claude Platform on AWS · stopped on its own

Sep 15, the whole day Question 31, every day

Exact recordShowThe 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-15 09:00:03 UTC (matches the pin)
Date: 2026-09-15 · run 20260915T090004Z-599f39 · scorer v1
Scored: answered
Changes: Minor Top-pick change: named a different first choice for a question about which JavaScript framework to start with
sha256: 22d7721816ac79b7078c5aa6be89d393da25d446fca333d66cc50c6957a58132
Permalink: https://modeldrift.watch/r/2026-09-15/P26/anthropic/claude-opus-5/

Scored: answered
Received: 2026-09-15 09:24:16 UTC
Run: 20260915T090004Z-599f39
Served by: Claude Platform on AWS · HTTP 200 · finish stop
Size: 2,338 characters · 2,229 tokens out incl. hidden reasoning · 35.1 s

Extracted picks, in order · confidence medium

Default answer React
Astro
SvelteKit
Angular

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

**Default answer: React, via Next.js if you need server rendering, or Vite + React + TanStack Router if it's a pure client-side app.**
Not because it's the most elegant — it isn't — but because the ecosystem gravity is overwhelming. Any library you need exists, any problem you hit has been Googled before, and you can hire for it. For most projects, that matters more than technical elegance.
That said, there are situations where something else is clearly better:
- **Content-heavy site** (marketing, docs, blog, mostly-static with some interactive bits) → **Astro**. Ships almost no JS by default, and you can drop React/Vue/Svelte components into islands where you actually need interactivity. Using Next.js for this is overkill.
- **Small team, velocity matters, hiring isn't a constraint** → **SvelteKit** or **Nuxt**. Both have materially better DX than Next. SvelteKit especially — less ceremony, smaller bundles, and the docs are excellent. The tradeoff is a thinner ecosystem of off-the-shelf components.
- **Large org, multiple teams, long-lived codebase** → **Angular** is a legitimate choice again. The signals-based rewrite modernized it considerably, and strong conventions plus batteries-included tooling reduce bikeshedding when you have 40 developers.
- **You already have a server-rendered backend** (Rails, Django, Laravel, Phoenix) → consider not adding a SPA framework at all. HTMX, Hotwire, or LiveView will get you most of the way with a fraction of the complexity.
Two honest caveats about the default recommendation. React's complexity has genuinely increased — Server Components and the Next.js App Router are powerful but have a real learning curve, and plenty of experienced developers find them frustrating. And Next.js has some coupling to Vercel's deployment model that's worth understanding before you commit. If neither appeals, SvelteKit is my second pick without much hesitation.
Things that will affect your outcome more than this decision: use TypeScript, pick what your team already knows if they know something, and check that your deployment target is well-supported before you're three months in.
One note — framework releases move fast and my information has a cutoff, so worth a quick sanity check on current versions.
What are you building? I can be more specific with a bit of context.

End of response · 18 lines · 2,338 characters · sha256 22d7721816ac79b7078c5aa6be89d393da25d446fca333d66cc50c6957a58132