MODELDRIFT.WATCH

Sep 11 · Day 2

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 10beforePermalink

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

Default recommendation: Next.js with TypeScript if you’re building a full-stack web product and want the broadest ecosystem, integrations, hosting options, and hiring pool.

Choose something else when the project points clearly toward it:

  • •React + Vite — client-side SPA; no need for SSR or a full-stack framework.
  • •SvelteKit — smaller team, simpler code, strong developer experience.
  • •Nuxt — your team prefers Vue.
  • •Astro — content-heavy sites, documentation, blogs, or marketing pages.
  • •Angular — large enterprise teams that value strict conventions.
  • •Expo — primarily a React Native mobile app.

Avoid choosing Next.js merely because it is popular: its server/client component model and caching can add complexity. Team familiarity usually matters more than benchmark differences.

If you provide the app type, team size, deployment target, and SEO requirements, I can give a more specific choice.

SEP 11afterPermalink

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

Default recommendation: TypeScript + React + Next.js.

It’s a strong general choice for a new production web app because of its ecosystem, hiring pool, routing, server rendering, API support, and broad hosting options.

Choose something else when the project suggests it:

  • •Vue + Nuxt — approachable syntax and excellent developer experience.
  • •SvelteKit — less boilerplate; great for small teams and highly interactive apps.
  • •Angular — structured, opinionated framework for large enterprise teams.
  • •Astro — best for content-heavy sites with limited client-side JavaScript.
  • •React or Vue with Vite — client-only dashboards/SPAs that don’t need SSR or full-stack framework features.

A practical rule:

  • •SaaS/product app → Next.js
  • •Content/marketing site → Astro
  • •Enterprise application → Angular
  • •Small team prioritizing simplicity → SvelteKit
  • •Unsure but dislike React’s style → Nuxt

Use TypeScript regardless. If you share whether the project is a dashboard, SaaS app, e-commerce site, or content site—and your team size—I can narrow it to one choice.

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

Before baseline

2026-09-10 permalink

Scored
answered
Received
2026-09-10 22:33:21 UTC
Run
20260910T221001Z-bb5bd1
Served by
OpenAI · HTTP 200 · finish stop
Size
939 characters · 448 tokens out incl. hidden reasoning · 9.7 s
Extracted picks, in order · confidence medium
  1. Next.js with TypeScript
  2. React + Vite
  3. SvelteKit
  4. Nuxt
  5. Astro
  6. Angular
  7. Expo

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

**Default recommendation:** **Next.js with TypeScript** if you’re building a full-stack web product and want the broadest ecosystem, integrations, hosting options, and hiring pool.
Choose something else when the project points clearly toward it:
- **React + Vite** — client-side SPA; no need for SSR or a full-stack framework.
- **SvelteKit** — smaller team, simpler code, strong developer experience.
- **Nuxt** — your team prefers Vue.
- **Astro** — content-heavy sites, documentation, blogs, or marketing pages.
- **Angular** — large enterprise teams that value strict conventions.
- **Expo** — primarily a React Native mobile app.
Avoid choosing Next.js merely because it is popular: its server/client component model and caching can add complexity. Team familiarity usually matters more than benchmark differences.
If you provide the app type, team size, deployment target, and SEO requirements, I can give a more specific choice.

End of response · 14 lines · 939 characters · sha256 77ce86a57e1acfaf8df9475c8c124a2204301db89d52d2e0f585a4e57038d1f8

After this run

2026-09-11 permalink

Scored
answered
Received
2026-09-11 09:29:09 UTC
Run
20260911T090002Z-da0dd3
Served by
OpenAI · HTTP 200 · finish stop
Size
1,115 characters · 492 tokens out incl. hidden reasoning · 17.5 s
Extracted picks, in order · confidence medium
  1. TypeScript + React + Next.js
  2. Vue + Nuxt
  3. SvelteKit
  4. Angular
  5. Astro
  6. React or Vue with Vite

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

**Default recommendation:** **TypeScript + React + Next.js**.
It’s a strong general choice for a new production web app because of its ecosystem, hiring pool, routing, server rendering, API support, and broad hosting options.
Choose something else when the project suggests it:
- **Vue + Nuxt** — approachable syntax and excellent developer experience.
- **SvelteKit** — less boilerplate; great for small teams and highly interactive apps.
- **Angular** — structured, opinionated framework for large enterprise teams.
- **Astro** — best for content-heavy sites with limited client-side JavaScript.
- **React or Vue with Vite** — client-only dashboards/SPAs that don’t need SSR or full-stack framework features.
A practical rule:
- SaaS/product app → **Next.js**
- Content/marketing site → **Astro**
- Enterprise application → **Angular**
- Small team prioritizing simplicity → **SvelteKit**
- Unsure but dislike React’s style → **Nuxt**
Use **TypeScript** regardless. If you share whether the project is a dashboard, SaaS app, e-commerce site, or content site—and your team size—I can narrow it to one choice.

End of response · 21 lines · 1,115 characters · sha256 d16494d193f9ce116a556573d8c3dcabd6cbbf835801a3fca0296a56207bea7e

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-11 09:00:01 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
0 added, 1 dropped
Baseline
1 prior day with data; 1 matched the baseline value (2026-09-10)
Responses
before 2026-09-10 22:33:21 UTC, run 20260910T221001Z-bb5bd1; after 2026-09-11 09:29:09 UTC, run 20260911T090002Z-da0dd3
Detected
2026-09-11 · run 20260911T090002Z-da0dd3, started 2026-09-11 09:00:02 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-11/P26/openai/gpt-5.6-sol/pick_change/picks/
Event ID
2026-09-11: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.