MODELDRIFT.WATCH

Sep 18 · Day 9

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 18afterPermalink

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

Default recommendation: Next.js with TypeScript.

Choose it for a typical production web app because it offers React’s ecosystem, server rendering, routing, backend endpoints, deployment options, and a large hiring/community base.

Choose something else when your project has a clearer fit:

  • •Nuxt — you prefer Vue.
  • •SvelteKit — you want less boilerplate and a simpler component model.
  • •Astro — content-heavy site, documentation, blog, or marketing site.
  • •Angular — large enterprise application needing strong conventions.
  • •React + Vite — purely client-side SPA; you don’t need SSR or a full-stack framework.
  • •React Router framework mode — React app where web standards and flexible deployment matter more than Next.js’s integrated platform model.

The strongest rule is: use the framework your team can operate confidently. If there are no team or product constraints, start with Next.js + TypeScript.

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-18 permalink

Scored
answered
Received
2026-09-18 09:27:31 UTC
Run
20260918T090022Z-92b6f7
Served by
OpenAI · HTTP 200 · finish stop
Size
944 characters · 441 tokens out incl. hidden reasoning · 13.3 s
Extracted picks, in order · confidence medium
  1. Next.js with TypeScript
  2. Nuxt
  3. SvelteKit
  4. Astro
  5. Angular
  6. React + Vite

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

**Default recommendation: Next.js with TypeScript.**
Choose it for a typical production web app because it offers React’s ecosystem, server rendering, routing, backend endpoints, deployment options, and a large hiring/community base.
Choose something else when your project has a clearer fit:
- **Nuxt** — you prefer Vue.
- **SvelteKit** — you want less boilerplate and a simpler component model.
- **Astro** — content-heavy site, documentation, blog, or marketing site.
- **Angular** — large enterprise application needing strong conventions.
- **React + Vite** — purely client-side SPA; you don’t need SSR or a full-stack framework.
- **React Router framework mode** — React app where web standards and flexible deployment matter more than Next.js’s integrated platform model.
The strongest rule is: **use the framework your team can operate confidently**. If there are no team or product constraints, start with **Next.js + TypeScript**.

End of response · 14 lines · 944 characters · sha256 2c4e10a1c50815326ca63be6a8213bdec6b66fcd4268c5ac42c19b7a3fdfb5b4

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-18 09:00:22 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-18 09:27:31 UTC, run 20260918T090022Z-92b6f7
Detected
2026-09-18 · run 20260918T090022Z-92b6f7, started 2026-09-18 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-18/P26/openai/gpt-5.6-sol/pick_change/picks/
Event ID
2026-09-18: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.