MODELDRIFT.WATCH

Sep 12 · Day 3

MINOR · GPT · QUESTION 31

GPT put its recommendations for a question about which JavaScript framework to start with in a new order.

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

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.

SEP 12afterPermalink

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

Default recommendation today: use TypeScript with React—but choose the project framework based on deployment needs.

  • •Full-stack app, SSR, SEO, or server-rendered pages: Next.js
  • •Client-side SPA or internal dashboard: React + Vite
  • •Prefer a gentler, more cohesive developer experience: Vue + Nuxt
  • •Small team wanting minimal boilerplate and excellent performance: SvelteKit
  • •Large enterprise team needing strict conventions: Angular
  • •Mostly content-driven site: Astro

If you have no special constraints, I’d start with:

  • •Next.js for a public production web application
  • •React + Vite for a client-only application

Don’t choose primarily from benchmarks; prioritize your team’s familiarity, required hosting model, ecosystem dependencies, and hiring needs. Use TypeScript regardless.

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

Before baseline

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

After this run

2026-09-12 permalink

Scored
answered
Received
2026-09-12 09:22:48 UTC
Run
20260912T090021Z-c0c86e
Served by
OpenAI · HTTP 200 · finish stop
Size
856 characters · 320 tokens out incl. hidden reasoning · 6.9 s
Extracted picks, in order · confidence medium
  1. Next.js
  2. React + Vite
  3. Vue + Nuxt
  4. SvelteKit
  5. Angular
  6. Astro

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

**Default recommendation today: use TypeScript with React—but choose the project framework based on deployment needs.**
- **Full-stack app, SSR, SEO, or server-rendered pages:** **Next.js**
- **Client-side SPA or internal dashboard:** **React + Vite**
- **Prefer a gentler, more cohesive developer experience:** **Vue + Nuxt**
- **Small team wanting minimal boilerplate and excellent performance:** **SvelteKit**
- **Large enterprise team needing strict conventions:** **Angular**
- **Mostly content-driven site:** **Astro**
If you have no special constraints, I’d start with:
- **Next.js** for a public production web application
- **React + Vite** for a client-only application
Don’t choose primarily from benchmarks; prioritize your team’s familiarity, required hosting model, ecosystem dependencies, and hiring needs. Use **TypeScript** regardless.

End of response · 15 lines · 856 characters · sha256 ec6a8d66dfd88a51efb11acef68178e1d532f9de41480d3e879adacbfe1d4bf3

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-12 09:00:20 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
2 prior days with data; 1 matched the baseline value (2026-09-11)
Responses
before 2026-09-11 09:29:09 UTC, run 20260911T090002Z-da0dd3; after 2026-09-12 09:22:48 UTC, run 20260912T090021Z-c0c86e
Detected
2026-09-12 · run 20260912T090021Z-c0c86e, started 2026-09-12 09:00:21 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-12/P26/openai/gpt-5.6-sol/pick_change/picks/
Event ID
2026-09-12: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.