MODELDRIFT.WATCH

Sep 26 · Day 17

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

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

Default recommendation: TypeScript + React.

Choose the setup based on the project:

  • •Full-stack site, SSR, SEO, e-commerce: Next.js
  • •Client-side dashboard or SPA: React + Vite
  • •Prefer simpler conventions and excellent developer experience: Vue + Nuxt
  • •Small team prioritizing minimal code and performance: SvelteKit
  • •Content-heavy site: Astro
  • •Enterprise team already standardized on Angular: Angular

If you have no special constraints, start with Next.js + TypeScript. It offers the broadest ecosystem, strong hiring availability, and flexibility for both static and server-rendered pages.

One caveat: don’t choose Next.js merely for a simple SPA—React + Vite is lighter and easier in that case.

SEP 26backPermalink

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

Default recommendation: Next.js with TypeScript for a typical production web application.

Choose something else when the project clearly fits:

  • •SvelteKit — smaller teams, simpler code, fast development
  • •Nuxt — your team prefers Vue
  • •Astro — content-heavy sites, documentation, blogs, marketing
  • •Angular — large enterprise teams wanting strong conventions
  • •Vite + React/Vue/Svelte — client-only apps that don’t need SSR, server routes, or full-stack features

Next.js is the safest general choice because of its ecosystem, hiring pool, rendering options, integrations, and deployment support. However, it adds complexity—especially around server/client component boundaries—so don’t use it for a simple SPA merely because it is popular.

Short rule:

  • •Building a SaaS or full-stack product with no strong preference → Next.js
  • •Optimizing for developer simplicity → SvelteKit
  • •Building mostly static content → Astro
  • •Existing team expertise → use the framework the team already knows well
Exact recordShowHideEach response verbatim, unrendered, with line numbers and its sha256

Deviation the day it changed

2026-09-25 permalink

Scored
answered
Received
2026-09-25 09:22:34 UTC
Run
20260925T090007Z-f08d1f
Served by
OpenAI · HTTP 200 · finish stop
Size
765 characters · 393 tokens out incl. hidden reasoning · 6.2 s
Extracted picks, in order · confidence medium
  1. TypeScript + React
  2. Next.js
  3. React + Vite
  4. Vue + Nuxt
  5. SvelteKit
  6. Astro
  7. Angular

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

**Default recommendation: TypeScript + React.**
Choose the setup based on the project:
- **Full-stack site, SSR, SEO, e-commerce:** **Next.js**
- **Client-side dashboard or SPA:** **React + Vite**
- **Prefer simpler conventions and excellent developer experience:** **Vue + Nuxt**
- **Small team prioritizing minimal code and performance:** **SvelteKit**
- **Content-heavy site:** **Astro**
- **Enterprise team already standardized on Angular:** **Angular**
If you have no special constraints, start with **Next.js + TypeScript**. It offers the broadest ecosystem, strong hiring availability, and flexibility for both static and server-rendered pages.
One caveat: don’t choose Next.js merely for a simple SPA—**React + Vite** is lighter and easier in that case.

End of response · 14 lines · 765 characters · sha256 379e60a70fdee8fd56a2b1365cf66a8304fd6f25cc6a198d8a9b74dc7fee2361

Reverted back to baseline

2026-09-26 permalink

Scored
answered
Received
2026-09-26 09:21:34 UTC
Run
20260926T090007Z-89c0b7
Served by
OpenAI · HTTP 200 · finish stop
Size
1,038 characters · 495 tokens out incl. hidden reasoning · 7.0 s
Extracted picks, in order · confidence medium
  1. Next.js with TypeScript
  2. SvelteKit
  3. Nuxt
  4. Astro
  5. Angular
  6. Vite + React/Vue/Svelte

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

**Default recommendation: Next.js with TypeScript** for a typical production web application.
Choose something else when the project clearly fits:
- **SvelteKit** — smaller teams, simpler code, fast development
- **Nuxt** — your team prefers Vue
- **Astro** — content-heavy sites, documentation, blogs, marketing
- **Angular** — large enterprise teams wanting strong conventions
- **Vite + React/Vue/Svelte** — client-only apps that don’t need SSR, server routes, or full-stack features
Next.js is the safest general choice because of its ecosystem, hiring pool, rendering options, integrations, and deployment support. However, it adds complexity—especially around server/client component boundaries—so don’t use it for a simple SPA merely because it is popular.
**Short rule:**
- Building a SaaS or full-stack product with no strong preference → **Next.js**
- Optimizing for developer simplicity → **SvelteKit**
- Building mostly static content → **Astro**
- Existing team expertise → use the framework the team already knows well

End of response · 17 lines · 1,038 characters · sha256 c2aa02aafc879c311181bfd110da3759ae67dbf55db5d404ecc811c5ac3e7504

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-26 09:00:06 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; 5 matched the baseline value (2026-09-18, 2026-09-19, 2026-09-20, 2026-09-23, 2026-09-25)
Responses
deviation 2026-09-25 09:22:34 UTC, run 20260925T090007Z-f08d1f; reverted 2026-09-26 09:21:34 UTC, run 20260926T090007Z-89c0b7
Detected
2026-09-26 · run 20260926T090007Z-89c0b7, started 2026-09-26 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-26/P26/openai/gpt-5.6-sol/transient_anomaly/picks.top/
Event ID
2026-09-26: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.