MODELDRIFT.WATCH

Sep 29 · Day 20

MINOR · GPT · QUESTION 31

GPT named a different first choice 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 28beforePermalink

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

Default recommendation: React + TypeScript, choosing the framework based on the app:

  • •Next.js — best general choice for a production web app needing routing, SSR/SEO, authentication, APIs, or full-stack features.
  • •Vite + React — better for a purely client-side SPA or when you want less framework complexity.
  • •Astro — best for content-heavy sites, documentation, blogs, and marketing pages.
  • •SvelteKit — excellent if you value simplicity and developer experience over ecosystem size.
  • •Nuxt — choose this if your team prefers Vue.
  • •Angular — strongest fit for large, structured enterprise teams.

If you have no special constraints and want the safest ecosystem, hiring pool, and library support, start with Next.js + TypeScript. Avoid adding extra state-management or backend libraries until the project actually needs them.

SEP 29afterPermalink

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.

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

Before baseline

2026-09-28 permalink

Scored
answered
Received
2026-09-28 09:22:12 UTC
Run
20260928T090007Z-07d4be
Served by
OpenAI · HTTP 200 · finish stop
Size
863 characters · 375 tokens out incl. hidden reasoning · 5.6 s
Extracted picks, in order · confidence medium
  1. React + TypeScript
  2. Next.js
  3. Vite + React
  4. Astro
  5. SvelteKit
  6. Nuxt
  7. Angular

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

**Default recommendation: React + TypeScript**, choosing the framework based on the app:
- **Next.js** — best general choice for a production web app needing routing, SSR/SEO, authentication, APIs, or full-stack features.
- **Vite + React** — better for a purely client-side SPA or when you want less framework complexity.
- **Astro** — best for content-heavy sites, documentation, blogs, and marketing pages.
- **SvelteKit** — excellent if you value simplicity and developer experience over ecosystem size.
- **Nuxt** — choose this if your team prefers Vue.
- **Angular** — strongest fit for large, structured enterprise teams.
If you have no special constraints and want the safest ecosystem, hiring pool, and library support, start with **Next.js + TypeScript**. Avoid adding extra state-management or backend libraries until the project actually needs them.

End of response · 10 lines · 863 characters · sha256 60a36ea0f1786ab3e8c7722e5d2934b9950533b9f9864480a64ed3354c9bf464

After this run

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

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-29 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; 3 matched the baseline value (2026-09-22, 2026-09-25, 2026-09-28)
Responses
before 2026-09-28 09:22:12 UTC, run 20260928T090007Z-07d4be; after 2026-09-29 09:23:11 UTC, run 20260929T090007Z-334891
Detected
2026-09-29 · run 20260929T090007Z-334891, started 2026-09-29 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-29/P26/openai/gpt-5.6-sol/pick_change/picks.top/
Event ID
2026-09-29:P26:openai/gpt-5.6-sol:pick_change: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.