MODELDRIFT.WATCH

Sep 14 · Day 5

MINOR · GPT · QUESTION 31

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

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

Default choice: Next.js with TypeScript if you’re building a typical production web app and want SSR, routing, APIs, authentication integrations, SEO, and a large ecosystem.

Choose differently when the project suggests it:

Project typeRecommended choice
Client-only SPA or internal dashboardReact + Vite
Full-stack React applicationNext.js
Content-heavy site, blog, or documentationAstro
Simpler, highly productive full-stack developmentSvelteKit
Team prefers VueNuxt
Large enterprise app with strong conventionsAngular

My practical rule:

  • •No special constraints: Next.js + TypeScript
  • •No server rendering needed: React + Vite + TypeScript
  • •Mostly content: Astro

Prefer the framework your team already knows unless it clearly conflicts with deployment, rendering, or maintenance requirements.

SEP 14afterPermalink

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

With no other context, start with TypeScript + React.

Choose the setup based on the project:

  • •Next.js — best general default for a production web app needing routing, server rendering, SEO, authentication, or backend endpoints.
  • •React + Vite — better for a client-side SPA, internal dashboard, or app with a separate backend.
  • •Vue + Nuxt — choose if you value a gentler learning curve and cohesive developer experience.
  • •SvelteKit — excellent for small teams prioritizing simplicity and performance, with a smaller ecosystem.
  • •Angular — strongest fit for large enterprise teams wanting strict conventions and an all-in-one framework.

My practical default:

Public/full-stack product: Next.js + TypeScript
Client-only application: React + Vite + TypeScript

If you describe the project—public site vs dashboard, team size, SEO needs, and backend—I can narrow it to one choice.

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

Before baseline

2026-09-13 permalink

Scored
answered
Received
2026-09-13 09:14:54 UTC
Run
20260913T090021Z-a7390a
Served by
OpenAI · HTTP 200 · finish stop
Size
909 characters · 549 tokens out incl. hidden reasoning · 11.4 s
Extracted picks, in order · confidence high
  1. Next.js with TypeScript
  2. React + Vite
  3. Astro
  4. SvelteKit
  5. Nuxt
  6. Angular

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

**Default choice:** **Next.js with TypeScript** if you’re building a typical production web app and want SSR, routing, APIs, authentication integrations, SEO, and a large ecosystem.
Choose differently when the project suggests it:
| Project type | Recommended choice |
|---|---|
| Client-only SPA or internal dashboard | **React + Vite** |
| Full-stack React application | **Next.js** |
| Content-heavy site, blog, or documentation | **Astro** |
| Simpler, highly productive full-stack development | **SvelteKit** |
| Team prefers Vue | **Nuxt** |
| Large enterprise app with strong conventions | **Angular** |
My practical rule:
- **No special constraints:** Next.js + TypeScript
- **No server rendering needed:** React + Vite + TypeScript
- **Mostly content:** Astro
Prefer the framework your team already knows unless it clearly conflicts with deployment, rendering, or maintenance requirements.

End of response · 20 lines · 909 characters · sha256 013caaed50b128e0835c7d9dce631244b2b08ded378e6c39ceffeae6b27fb03a

After this run

2026-09-14 permalink

Scored
answered
Received
2026-09-14 09:26:56 UTC
Run
20260914T090022Z-e98262
Served by
OpenAI · HTTP 200 · finish stop
Size
919 characters · 385 tokens out incl. hidden reasoning · 116.2 s
Extracted picks, in order · confidence medium
  1. Next.js
  2. React + Vite
  3. Vue + Nuxt
  4. SvelteKit
  5. Angular

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

**With no other context, start with TypeScript + React.**
Choose the setup based on the project:
- **Next.js** — best general default for a production web app needing routing, server rendering, SEO, authentication, or backend endpoints.
- **React + Vite** — better for a client-side SPA, internal dashboard, or app with a separate backend.
- **Vue + Nuxt** — choose if you value a gentler learning curve and cohesive developer experience.
- **SvelteKit** — excellent for small teams prioritizing simplicity and performance, with a smaller ecosystem.
- **Angular** — strongest fit for large enterprise teams wanting strict conventions and an all-in-one framework.
My practical default:
```text
Public/full-stack product: Next.js + TypeScript
Client-only application: React + Vite + TypeScript
```
If you describe the project—public site vs dashboard, team size, SEO needs, and backend—I can narrow it to one choice.

End of response · 18 lines · 919 characters · sha256 2b20c2e1046dccd3fdb41aaaeecb1087883f7a3e0654510d8c8c0e1bbc45545c

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-14 09:00:21 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
0 added, 1 dropped
Baseline
4 prior days with data; 1 matched the baseline value (2026-09-13)
Responses
before 2026-09-13 09:14:54 UTC, run 20260913T090021Z-a7390a; after 2026-09-14 09:26:56 UTC, run 20260914T090022Z-e98262
Detected
2026-09-14 · run 20260914T090022Z-e98262, started 2026-09-14 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-14/P26/openai/gpt-5.6-sol/pick_change/picks/
Event ID
2026-09-14:P26:openai/gpt-5.6-sol: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.