MODELDRIFT.WATCH

Sep 30 · Day 21

MINOR · GPT · QUESTION 31

GPT went back to its earlier list for a question about which JavaScript framework to start with.

Why it’s minor

The change lasted one day before the model went back.

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 29the changePermalink

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

Default recommendation: Next.js with TypeScript.

It’s the safest general-purpose choice for a new web application because it offers:

  • •React’s large ecosystem and hiring pool
  • •Server-side rendering and static generation
  • •Routing, API endpoints, and deployment conventions built in
  • •Good support across hosting providers

Choose something else when your priorities differ:

  • •Vite + React — client-only SPA; you don’t need SSR or full-stack framework features.
  • •Nuxt — you prefer Vue’s simpler component model.
  • •SvelteKit — smaller teams prioritizing simplicity and minimal boilerplate.
  • •Astro — content-heavy sites, blogs, documentation, or mostly static pages.
  • •Angular — large enterprise teams wanting strong conventions and integrated tooling.
  • •Remix / React Router framework mode — web-standard, form-heavy applications with less emphasis on React Server Components.

If you have no stronger preference, use Next.js + TypeScript, start with the simplest rendering model that works, and avoid adding state libraries until you actually need one.

SEP 30backPermalink

Picks read from the answer, in order
  1. React + TypeScript
  2. Next.js
  3. Vite

Default recommendation: start with React + TypeScript, using:

  • •Next.js for a full-stack app, public website, SEO, server rendering, or API routes.
  • •Vite for a client-only SPA or when the backend is separate.

Choose something else when priorities differ:

  • •Vue + Nuxt: easier learning curve and excellent conventions.
  • •Svelte + SvelteKit: minimal boilerplate and a highly productive developer experience.
  • •Angular: large enterprise teams needing strict structure and long-term consistency.
  • •Astro: content-heavy sites where minimal client-side JavaScript matters.

If I had no other project details, I’d choose Next.js with TypeScript, while avoiding unnecessary server components or complex caching until the app actually needs them. For a simple dashboard backed by an existing API, I’d choose React + Vite instead.

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

Deviation the day it changed

2026-09-29 permalink

Scored
answered
Received
2026-09-29 09:23:11 UTC
Run
20260929T090007Z-334891
Served by
OpenAI · HTTP 200 · finish stop
Size
1,089 characters · 491 tokens out incl. hidden reasoning · 8.0 s
Extracted picks, in order · confidence medium
  1. Next.js with TypeScript
  2. Vite + React
  3. Nuxt
  4. SvelteKit
  5. Astro
  6. Angular
  7. Remix / React Router framework mode

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

**Default recommendation: Next.js with TypeScript.**
It’s the safest general-purpose choice for a new web application because it offers:
- React’s large ecosystem and hiring pool
- Server-side rendering and static generation
- Routing, API endpoints, and deployment conventions built in
- Good support across hosting providers
Choose something else when your priorities differ:
- **Vite + React** — client-only SPA; you don’t need SSR or full-stack framework features.
- **Nuxt** — you prefer Vue’s simpler component model.
- **SvelteKit** — smaller teams prioritizing simplicity and minimal boilerplate.
- **Astro** — content-heavy sites, blogs, documentation, or mostly static pages.
- **Angular** — large enterprise teams wanting strong conventions and integrated tooling.
- **Remix / React Router framework mode** — web-standard, form-heavy applications with less emphasis on React Server Components.
If you have no stronger preference, use **Next.js + TypeScript**, start with the simplest rendering model that works, and avoid adding state libraries until you actually need one.

End of response · 19 lines · 1,089 characters · sha256 d7756f39376687cff748c4abf84d8043b6aab6feb8a188b01cdfe42616b8a66c

Reverted back to baseline

2026-09-30 permalink

Scored
answered
Received
2026-09-30 09:21:19 UTC
Run
20260930T090007Z-45ce12
Served by
OpenAI · HTTP 200 · finish stop
Size
864 characters · 268 tokens out incl. hidden reasoning · 4.5 s
Extracted picks, in order · confidence medium
  1. React + TypeScript
  2. Next.js
  3. Vite

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

**Default recommendation:** start with **React + TypeScript**, using:
- **Next.js** for a full-stack app, public website, SEO, server rendering, or API routes.
- **Vite** for a client-only SPA or when the backend is separate.
Choose something else when priorities differ:
- **Vue + Nuxt:** easier learning curve and excellent conventions.
- **Svelte + SvelteKit:** minimal boilerplate and a highly productive developer experience.
- **Angular:** large enterprise teams needing strict structure and long-term consistency.
- **Astro:** content-heavy sites where minimal client-side JavaScript matters.
If I had no other project details, I’d choose **Next.js with TypeScript**, while avoiding unnecessary server components or complex caching until the app actually needs them. For a simple dashboard backed by an existing API, I’d choose **React + Vite** instead.

End of response · 13 lines · 864 characters · sha256 a115648e54922f6d93a5f0425dbd82cb9ca2d2587ce5d30e857b0c2b70e00cc2

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-30 09:00:07 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
6 prior days with data; 4 matched the baseline value (2026-09-22, 2026-09-25, 2026-09-28, 2026-09-29)
Responses
deviation 2026-09-29 09:23:11 UTC, run 20260929T090007Z-334891; reverted 2026-09-30 09:21:19 UTC, run 20260930T090007Z-45ce12
Detected
2026-09-30 · run 20260930T090007Z-45ce12, started 2026-09-30 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-30/P26/openai/gpt-5.6-sol/transient_anomaly/picks.top/
Event ID
2026-09-30:P26:openai/gpt-5.6-sol:transient_anomaly: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.