MODELDRIFT.WATCH

Sep 17 · Day 8

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

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

Default recommendation: start with React + Next.js + TypeScript.

Why:

  • •Largest ecosystem and hiring pool
  • •Strong support for server rendering, routing, APIs, and deployment
  • •Easy to find libraries, examples, and maintainers
  • •Suitable for prototypes through large production apps

Choose something else when:

  • •Vue + Nuxt — you want a gentler learning curve and clean templates.
  • •Svelte + SvelteKit — you value simplicity, compact code, and excellent performance.
  • •Angular — you’re building a large enterprise app that benefits from a highly opinionated, all-in-one framework.
  • •Vite + React/Vue/Svelte — it’s a client-only SPA and you don’t need a full-stack framework.
  • •Astro — it’s primarily a content, marketing, or documentation site with limited interactivity.

If you have no special constraints, use:

Next.js + React + TypeScript

For a mostly client-side application, use:

Vite + React + TypeScript

The best choice ultimately depends on whether the project needs SSR/SEO, server APIs, mobile support, and what your team already knows.

SEP 17backPermalink

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.

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

Deviation the day it changed

2026-09-16 permalink

Scored
answered
Received
2026-09-16 09:23:57 UTC
Run
20260916T090004Z-fdcf7b
Served by
OpenAI · HTTP 200 · finish stop
Size
1,106 characters · 329 tokens out incl. hidden reasoning · 5.0 s
Extracted picks, in order · confidence medium
  1. React + Next.js + TypeScript
  2. Vue + Nuxt
  3. Svelte + SvelteKit
  4. Angular
  5. Vite + React/Vue/Svelte
  6. Astro

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

**Default recommendation:** start with **React + Next.js + TypeScript**.
Why:
- Largest ecosystem and hiring pool
- Strong support for server rendering, routing, APIs, and deployment
- Easy to find libraries, examples, and maintainers
- Suitable for prototypes through large production apps
Choose something else when:
- **Vue + Nuxt** — you want a gentler learning curve and clean templates.
- **Svelte + SvelteKit** — you value simplicity, compact code, and excellent performance.
- **Angular** — you’re building a large enterprise app that benefits from a highly opinionated, all-in-one framework.
- **Vite + React/Vue/Svelte** — it’s a client-only SPA and you don’t need a full-stack framework.
- **Astro** — it’s primarily a content, marketing, or documentation site with limited interactivity.
If you have no special constraints, use:
```text
Next.js + React + TypeScript
```
For a mostly client-side application, use:
```text
Vite + React + TypeScript
```
The best choice ultimately depends on whether the project needs SSR/SEO, server APIs, mobile support, and what your team already knows.

End of response · 29 lines · 1,106 characters · sha256 9537a46fbaddec7907e5ce12e5d27c7986875c4831a84000c2bd604885e6a34e

Reverted back to 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

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-17 09:00:21 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
same picks, new order
Baseline
7 prior days with data; 2 matched the baseline value (2026-09-15, 2026-09-16)
Responses
deviation 2026-09-16 09:23:57 UTC, run 20260916T090004Z-fdcf7b; reverted 2026-09-17 09:24:29 UTC, run 20260917T090022Z-136fc3
Detected
2026-09-17 · run 20260917T090022Z-136fc3, started 2026-09-17 09:00:22 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-17/P26/openai/gpt-5.6-sol/transient_anomaly/picks/
Event ID
2026-09-17:P26:openai/gpt-5.6-sol:transient_anomaly: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.