MODELDRIFT.WATCH

Sep 20 · Day 11

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 17beforePermalink

Picks read from the answer, in order
  1. Next.js with TypeScript

Default recommendation: Next.js with TypeScript if you’re building a typical production web application and don’t have stronger constraints. It offers a large ecosystem, straightforward hosting, server rendering, API routes, and broad hiring/community support.

Choose differently when the project points elsewhere:

  • •Client-only SPA: React + Vite
  • •Simpler, highly productive full-stack development: SvelteKit
  • •Prefer Vue: Nuxt
  • •Content-heavy site, blog, or documentation: Astro
  • •Large, convention-heavy enterprise application: Angular
  • •Mostly backend/API: Use a backend framework such as Fastify or NestJS rather than forcing it into a frontend framework

A practical rule:

  • •Need SEO, authentication, server rendering, and backend endpoints → Next.js
  • •Need an internal dashboard with no SEO → React + Vite
  • •Want minimal boilerplate and have flexibility in hiring/stack → SvelteKit
  • •Mostly static content with a little interactivity → Astro

Whichever you choose, start with TypeScript, enable strict mode, and avoid adding state-management libraries until the application genuinely needs them.

SEP 20afterPermalink

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.

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

Before baseline

2026-09-17 permalink

Scored
answered
Received
2026-09-17 09:24:29 UTC
Run
20260917T090022Z-136fc3
Served by
OpenAI · HTTP 200 · finish stop
Size
1,153 characters · 502 tokens out incl. hidden reasoning · 9.1 s
Extracted picks, in order · confidence low
  1. Next.js with TypeScript

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

**Default recommendation: Next.js with TypeScript** if you’re building a typical production web application and don’t have stronger constraints. It offers a large ecosystem, straightforward hosting, server rendering, API routes, and broad hiring/community support.
Choose differently when the project points elsewhere:
- **Client-only SPA:** React + Vite
- **Simpler, highly productive full-stack development:** SvelteKit
- **Prefer Vue:** Nuxt
- **Content-heavy site, blog, or documentation:** Astro
- **Large, convention-heavy enterprise application:** Angular
- **Mostly backend/API:** Use a backend framework such as Fastify or NestJS rather than forcing it into a frontend framework
A practical rule:
- Need SEO, authentication, server rendering, and backend endpoints → **Next.js**
- Need an internal dashboard with no SEO → **React + Vite**
- Want minimal boilerplate and have flexibility in hiring/stack → **SvelteKit**
- Mostly static content with a little interactivity → **Astro**
Whichever you choose, start with **TypeScript**, enable strict mode, and avoid adding state-management libraries until the application genuinely needs them.

End of response · 19 lines · 1,153 characters · sha256 2d29fa7bae5ac10a3ea04b78a31d49b778957eee228efee8e50a63d155ce1992

After this run

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

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-20 09:00:19 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
5 added, 0 dropped
Baseline
7 prior days with data; 2 matched the baseline value (2026-09-15, 2026-09-17)
Responses
before 2026-09-17 09:24:29 UTC, run 20260917T090022Z-136fc3; after 2026-09-20 09:23:14 UTC, run 20260920T090019Z-bbedf3
Detected
2026-09-20 · run 20260920T090019Z-bbedf3, started 2026-09-20 09:00:19 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-20/P26/openai/gpt-5.6-sol/pick_change/picks/
Event ID
2026-09-20: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.