MODELDRIFT.WATCH

Sep 21 · Day 12

MINOR · GPT · QUESTION 31

GPT 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 20beforePermalink

Picks read from the answer, in order
  1. React with Next.js and TypeScript
  2. Vue + Nuxt
  3. Svelte + SvelteKit
  4. Angular
  5. React + Vite
  6. Astro

Default recommendation: React with Next.js and TypeScript.

Choose it if you want the safest general-purpose option: a large ecosystem, strong hiring market, server rendering, routing, API support, and broad hosting compatibility.

Better choices for specific priorities:

  • •Vue + Nuxt — easier learning curve and excellent developer experience.
  • •Svelte + SvelteKit — less boilerplate and great for small teams, though the ecosystem is smaller.
  • •Angular — best for large enterprise teams needing strict conventions and built-in tooling.
  • •React + Vite — preferable to Next.js for a client-only SPA that doesn’t need SSR.
  • •Astro — best for content-heavy sites with limited interactivity.

If you have no special constraints, start with:

Next.js + TypeScript + ESLint

Use its current recommended router, start with server-rendered components where appropriate, and add libraries only when you need them.

SEP 21afterPermalink

Picks read from the answer, in order
  1. TypeScript + React
  2. Next.js
  3. React + Vite
  4. Vue + Nuxt
  5. Svelte + SvelteKit
  6. Angular

Default recommendation: use TypeScript + React.

  • •Full-stack app, SSR, SEO, or server-rendered pages: Next.js
  • •Client-side SPA with a separate backend: React + Vite
  • •Prefer simpler templates and a gentler learning curve: Vue + Nuxt
  • •Want minimal boilerplate and excellent developer experience: Svelte + SvelteKit
  • •Large enterprise team needing strong conventions: Angular

If I had to choose for a typical new production project today, I’d pick:

Next.js with TypeScript for a full-stack web application, or React + Vite when the backend is separate.

Before deciding, prioritize your team’s existing expertise, required libraries, hosting model, SEO needs, and whether you actually need server rendering.

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

Before baseline

2026-09-20 permalink

Scored
answered
Received
2026-09-20 09:23:14 UTC
Run
20260920T090019Z-bbedf3
Served by
OpenAI · HTTP 200 · finish stop
Size
942 characters · 378 tokens out incl. hidden reasoning · 5.6 s
Extracted picks, in order · confidence medium
  1. React with Next.js and TypeScript
  2. Vue + Nuxt
  3. Svelte + SvelteKit
  4. Angular
  5. React + Vite
  6. Astro

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

**Default recommendation: React with Next.js and TypeScript.**
Choose it if you want the safest general-purpose option: a large ecosystem, strong hiring market, server rendering, routing, API support, and broad hosting compatibility.
Better choices for specific priorities:
- **Vue + Nuxt** — easier learning curve and excellent developer experience.
- **Svelte + SvelteKit** — less boilerplate and great for small teams, though the ecosystem is smaller.
- **Angular** — best for large enterprise teams needing strict conventions and built-in tooling.
- **React + Vite** — preferable to Next.js for a client-only SPA that doesn’t need SSR.
- **Astro** — best for content-heavy sites with limited interactivity.
If you have no special constraints, start with:
```text
Next.js + TypeScript + ESLint
```
Use its current recommended router, start with server-rendered components where appropriate, and add libraries only when you need them.

End of response · 19 lines · 942 characters · sha256 3311e230b15c6f06176f46a61e91bac798a0d250d3882cdcd16a84ffe6286b23

After this run

2026-09-21 permalink

Scored
answered
Received
2026-09-21 09:24:54 UTC
Run
20260921T090021Z-989a7c
Served by
OpenAI · HTTP 200 · finish stop
Size
768 characters · 287 tokens out incl. hidden reasoning · 6.4 s
Extracted picks, in order · confidence medium
  1. TypeScript + React
  2. Next.js
  3. React + Vite
  4. Vue + Nuxt
  5. Svelte + SvelteKit
  6. Angular

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

**Default recommendation:** use **TypeScript + React**.
- **Full-stack app, SSR, SEO, or server-rendered pages:** **Next.js**
- **Client-side SPA with a separate backend:** **React + Vite**
- **Prefer simpler templates and a gentler learning curve:** **Vue + Nuxt**
- **Want minimal boilerplate and excellent developer experience:** **Svelte + SvelteKit**
- **Large enterprise team needing strong conventions:** **Angular**
If I had to choose for a typical new production project today, I’d pick:
> **Next.js with TypeScript** for a full-stack web application, or **React + Vite** when the backend is separate.
Before deciding, prioritize your team’s existing expertise, required libraries, hosting model, SEO needs, and whether you actually need server rendering.

End of response · 13 lines · 768 characters · sha256 dac586bde7c01d2645720c629d0347de682d8c65eeb288147dad8c65772d85e1

Record detailsShowHideModel version, runs, baseline, triage, permalink, event ID
Model
openai/gpt-5.6-sol
pinned openai/gpt-5.6-sol-20260709; alias resolved to openai/gpt-5.6-sol-20260709 at 2026-09-21 09:00:20 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; 7 matched the baseline value (2026-09-14, 2026-09-15, 2026-09-16, 2026-09-17, 2026-09-18, 2026-09-19, 2026-09-20)
Responses
before 2026-09-20 09:23:14 UTC, run 20260920T090019Z-bbedf3; after 2026-09-21 09:24:54 UTC, run 20260921T090021Z-989a7c
Detected
2026-09-21 · run 20260921T090021Z-989a7c, started 2026-09-21 09:00:21 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-21/P26/openai/gpt-5.6-sol/pick_change/picks.top/
Event ID
2026-09-21:P26:openai/gpt-5.6-sol: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.