MODELDRIFT.WATCH

Sep 23 · Day 14

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

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, SSR, authentication, SEO, or server-rendered pages.
  • •Vite for a client-side SPA that talks to a separate backend.

Choose something else when your priorities differ:

  • •Vue + Nuxt: easier learning curve and cohesive developer experience.
  • •Svelte + SvelteKit: minimal boilerplate and highly productive UI development.
  • •Angular: large enterprise teams that value strict conventions and built-in architecture.
  • •Astro: content-heavy sites, documentation, blogs, or mostly static pages with limited interactivity.
  • •React Native/Expo: mobile apps.

If you have no strong preference and expect to hire developers or use a broad ecosystem, Next.js + TypeScript is the safest general-purpose choice. If you want the simplest pleasant experience for a small team, I’d seriously consider Nuxt or SvelteKit.

SEP 23backPermalink

Picks read from the answer, in order
  1. Next.js with TypeScript
  2. React + Vite
  3. Vue + Nuxt
  4. SvelteKit
  5. Astro
  6. Angular
  7. Plain HTML/CSS/JavaScript

Default recommendation: Next.js with TypeScript.

Choose it for a typical production web app because it offers:

  • •A large React ecosystem and hiring pool
  • •Server rendering, static generation, routing, and API endpoints
  • •Strong hosting and tooling support
  • •Flexibility to scale from a small site to a full-stack application

Choose something else when the project points clearly toward it:

Project typeRecommended choice
Client-only SPA or internal dashboardReact + Vite
Prefer simpler, approachable developmentVue + Nuxt
Small team prioritizing concise, modern codeSvelteKit
Content-heavy site, blog, or documentationAstro
Large enterprise team needing strict conventionsAngular
Simple static pagePlain HTML/CSS/JavaScript

If you have no special constraints, use Next.js + TypeScript, add as few dependencies as possible, and avoid adopting advanced server features until the application actually needs them.

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

Deviation the day it changed

2026-09-22 permalink

Scored
answered
Received
2026-09-22 09:24:42 UTC
Run
20260922T090022Z-7ff13b
Served by
OpenAI · HTTP 200 · finish stop
Size
943 characters · 335 tokens out incl. hidden reasoning · 7.3 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, SSR, authentication, SEO, or server-rendered pages.
- **Vite** for a client-side SPA that talks to a separate backend.
Choose something else when your priorities differ:
- **Vue + Nuxt:** easier learning curve and cohesive developer experience.
- **Svelte + SvelteKit:** minimal boilerplate and highly productive UI development.
- **Angular:** large enterprise teams that value strict conventions and built-in architecture.
- **Astro:** content-heavy sites, documentation, blogs, or mostly static pages with limited interactivity.
- **React Native/Expo:** mobile apps.
If you have no strong preference and expect to hire developers or use a broad ecosystem, **Next.js + TypeScript** is the safest general-purpose choice. If you want the simplest pleasant experience for a small team, I’d seriously consider **Nuxt** or **SvelteKit**.

End of response · 14 lines · 943 characters · sha256 05ff677f1f8bba050b32b40dd73127970be90edd598f4d724ff62da476e808ce

Reverted back to baseline

2026-09-23 permalink

Scored
answered
Received
2026-09-23 09:22:18 UTC
Run
20260923T090022Z-9b7b3a
Served by
OpenAI · HTTP 200 · finish stop
Size
1,005 characters · 463 tokens out incl. hidden reasoning · 9.8 s
Extracted picks, in order · confidence high
  1. Next.js with TypeScript
  2. React + Vite
  3. Vue + Nuxt
  4. SvelteKit
  5. Astro
  6. Angular
  7. Plain HTML/CSS/JavaScript

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

**Default recommendation: Next.js with TypeScript**.
Choose it for a typical production web app because it offers:
- A large React ecosystem and hiring pool
- Server rendering, static generation, routing, and API endpoints
- Strong hosting and tooling support
- Flexibility to scale from a small site to a full-stack application
Choose something else when the project points clearly toward it:
| Project type | Recommended choice |
|---|---|
| Client-only SPA or internal dashboard | **React + Vite** |
| Prefer simpler, approachable development | **Vue + Nuxt** |
| Small team prioritizing concise, modern code | **SvelteKit** |
| Content-heavy site, blog, or documentation | **Astro** |
| Large enterprise team needing strict conventions | **Angular** |
| Simple static page | Plain **HTML/CSS/JavaScript** |
If you have no special constraints, use **Next.js + TypeScript**, add as few dependencies as possible, and avoid adopting advanced server features until the application actually needs them.

End of response · 21 lines · 1,005 characters · sha256 9afe3de15e572718acfa7e16743ecd126e93e3c19e24c7333ad8a938af5c71b3

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-23 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
first extracted pick differs from the baseline's (full lists below)
Baseline
7 prior days with data; 7 matched the baseline value (2026-09-15, 2026-09-16, 2026-09-17, 2026-09-18, 2026-09-19, 2026-09-20, 2026-09-22)
Responses
deviation 2026-09-22 09:24:42 UTC, run 20260922T090022Z-7ff13b; reverted 2026-09-23 09:22:18 UTC, run 20260923T090022Z-9b7b3a
Detected
2026-09-23 · run 20260923T090022Z-9b7b3a, started 2026-09-23 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-23/P26/openai/gpt-5.6-sol/transient_anomaly/picks.top/
Event ID
2026-09-23: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.