MODELDRIFT.WATCH

Sep 13 · Day 4

MINOR · GEMINI · QUESTION 31

Gemini 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 12the changePermalink

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

The best JavaScript framework for your new project depends entirely on what you are building, your team's experience, and your goals.

Today, the industry standard has moved away from basic single-page applications (SPAs) to meta-frameworks that handle routing, server-side rendering (SSR), and API endpoints out of the box.

Here is the breakdown of what you should choose today, categorized by project type:

1. The "Safe Bet" & Industry Standard: Next.js (React)

If you aren't sure what to pick, pick this. Next.js is built on top of React and is currently the dominant force in the JavaScript ecosystem.

  • •Best for: SaaS products, e-commerce, complex web apps, and projects where you might need to hire developers later.
  • •Pros: Massive ecosystem, endless UI libraries (like shadcn/ui or Tailwind UI), excellent documentation, and strong backing by Vercel.
  • •Cons: It can be overly complex for simple sites, and the recent shift to the "App Router" has a steep learning curve.

2. The Best Developer Experience: SvelteKit (Svelte)

If you want to write less code, have blazing-fast performance, and genuinely enjoy the development process, choose SvelteKit.

  • •Best for: Highly interactive dashboards, solo developers, and teams that want maximum performance without the complexity of React.
  • •Pros: No virtual DOM (it compiles to vanilla JS), incredibly intuitive syntax, built-in state management, and minimal boilerplate.
  • •Cons: Smaller ecosystem than React. You might have to build custom UI components rather than downloading pre-made ones.

3. For Content-Heavy & Marketing Sites: Astro

If you are building a website where content and SEO are the main focus, Astro is the absolute best choice today.

  • •Best for: Blogs, marketing websites, portfolios, documentation, and e-commerce storefronts.
  • •Pros: It ships zero JavaScript by default, making it insanely fast. It uses an "Islands Architecture," meaning you can use React, Vue, or Svelte components only where you need interactivity (like a shopping cart or image carousel).
  • •Cons: Not designed for highly complex, logged-in, app-like dashboards (though it is improving in this area).

4. The Balanced Middle-Ground: Nuxt (Vue.js)

If you like the structure of Angular but the flexibility of React, Nuxt (built on Vue) is a fantastic choice.

  • •Best for: Medium-to-large web apps, teams transitioning from traditional HTML/CSS web dev, and projects needing excellent organization.
  • •Pros: Vue’s Composition API is incredibly clean. Nuxt handles routing, state, and server-side rendering beautifully with less configuration than Next.js.
  • •Cons: The ecosystem is smaller than React's, and the transition from Vue 2 to Vue 3 fractured the community slightly (though this has mostly stabilized).

5. The Enterprise Heavyweight: Angular

If you are working in a large corporate environment with large teams, Angular remains a powerhouse. (Note: Angular recently had a massive renaissance with version 17+, making it much faster and easier to use).

  • •Best for: Massive enterprise applications, banking software, and projects where strict architecture and consistency across a large team are required.
  • •Pros: Everything is included (routing, HTTP client, form validation). It forces a strict structure so every Angular project looks similar.
  • •Cons: The steepest learning curve of the group. Very verbose.

Summary: How to decide right now

  • •Choose Next.js (React) if you want the most secure choice, the largest community, and access to the most third-party libraries.
  • •Choose Astro if you are building a website focused on content, SEO, and speed (like a blog or marketing site).
  • •Choose SvelteKit if you want the absolute best developer experience, fast performance, and hate complex boilerplate code.
  • •Choose Nuxt (Vue) if you want a clean, highly organized, and intuitive framework that sits perfectly between React and Angular.

TL;DR: If you want to get a job or build a startup fast using off-the-shelf templates, use Next.js. If you want to have fun coding and build a lightning-fast app, use SvelteKit.

SEP 13backPermalink

Picks read from the answer, in order
  1. Meta-frameworks
  2. Next.js
  3. SvelteKit
  4. Astro
  5. Nuxt
  6. Angular

Because you are starting a project today, the JavaScript landscape has shifted away from traditional Single Page Applications (SPAs) like Create React App and moved toward Meta-frameworks (frameworks built on top of React, Vue, etc. that handle routing and server-side rendering).

Since I don't know the exact nature of your project, here is the TL;DR breakdown of what you should choose based on your goals:

1. The "I want to get a job / Build a Startup" choice: Next.js (React)

Next.js is the undisputed industry standard right now. If you are building a complex SaaS, a startup, or want to make yourself as employable as possible, this is the answer.

  • •The Good: Massive ecosystem, you can find a library for literally anything, huge community support, and it handles both frontend and backend in one repository.
  • •The Bad: The introduction of the App Router and React Server Components (RSC) has made the learning curve steeper. It can feel overly complex for simple projects.
  • •Alternative: If you want to use React but Next.js feels too bloated, use Vite + React.

2. The "I want the best Developer Experience (DX)" choice: SvelteKit (Svelte)

Svelte consistently ranks as the most loved framework by developers. Instead of using a Virtual DOM like React, Svelte compiles your code into tiny, vanilla JavaScript.

  • •The Good: Incredibly fast, writes like traditional HTML/CSS/JS (very little boilerplate), state management is effortless, and it's incredibly fun to use.
  • •The Bad: Smaller ecosystem than React. You might have to build some components from scratch that you could otherwise just download in the React ecosystem. Job market is smaller.

3. The "Content / Blog / Marketing Site" choice: Astro

If you are building a portfolio, a blog, a documentation site, or a marketing landing page, you should use Astro.

  • •The Good: It ships zero JavaScript to the browser by default, making it blazingly fast for SEO. It uses "Islands Architecture," meaning you can write your UI in React, Vue, or Svelte, and Astro will only load JS for the specific interactive parts you tell it to.
  • •The Bad: Not designed for highly complex, logged-in dashboard applications (though they are working on closing this gap).

4. The "Sweet Spot" choice: Nuxt (Vue.js)

Vue has always sat perfectly between the rigid structure of Angular and the chaotic freedom of React. Nuxt is the meta-framework for Vue.

  • •The Good: Extremely intuitive, excellent documentation, and very clean code. The latest version of Nuxt is incredibly powerful and fast. It is heavily used in Europe and Asia.
  • •The Bad: The US job market heavily favors React over Vue.

5. The "Massive Enterprise" choice: Angular

Angular is backed by Google and provides a "batteries-included" experience. It dictates exactly how your code should be structured, making it great for massive teams.

  • •The Good: Angular recently underwent a massive modern renaissance (v17+). With the introduction of "Signals" and standalone components, it is faster and easier to write than it has been in years.
  • •The Bad: Very steep learning curve. It uses TypeScript heavily and relies on complex concepts like RxJS. Overkill for small projects.

📝 Your Decision Matrix:

  • 1.Are you building a blog, portfolio, or landing page? $\rightarrow$ Astro
  • 2.Are you optimizing for getting hired? $\rightarrow$ Next.js
  • 3.Are you building a complex SaaS and want to move fast with minimal headaches? $\rightarrow$ SvelteKit or Nuxt
  • 4.Are you building a massive corporate app with 20+ developers? $\rightarrow$ Angular or Next.js

My personal recommendation for a solo developer today:
If it's an interactive web app, choose SvelteKit. If it's a content site, choose Astro. If you need an expansive ecosystem of pre-built UI components, choose Next.js.

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

Deviation the day it changed

2026-09-12 permalink

Scored
answered
Received
2026-09-12 09:23:33 UTC
Run
20260912T090021Z-c0c86e
Served by
Google · HTTP 200 · finish stop
Size
4,234 characters · 2,140 tokens out incl. hidden reasoning · 19.1 s
Extracted picks, in order · confidence high
  1. Next.js
  2. SvelteKit
  3. Astro
  4. Nuxt
  5. Angular

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

The best JavaScript framework for your new project depends entirely on what you are building, your team's experience, and your goals.
Today, the industry standard has moved away from basic single-page applications (SPAs) to **meta-frameworks** that handle routing, server-side rendering (SSR), and API endpoints out of the box.
Here is the breakdown of what you should choose today, categorized by project type:
---
### 1. The "Safe Bet" & Industry Standard: Next.js (React)
If you aren't sure what to pick, pick this. **Next.js** is built on top of React and is currently the dominant force in the JavaScript ecosystem.
* **Best for:** SaaS products, e-commerce, complex web apps, and projects where you might need to hire developers later.
* **Pros:** Massive ecosystem, endless UI libraries (like shadcn/ui or Tailwind UI), excellent documentation, and strong backing by Vercel.
* **Cons:** It can be overly complex for simple sites, and the recent shift to the "App Router" has a steep learning curve.
### 2. The Best Developer Experience: SvelteKit (Svelte)
If you want to write less code, have blazing-fast performance, and genuinely enjoy the development process, choose **SvelteKit**.
* **Best for:** Highly interactive dashboards, solo developers, and teams that want maximum performance without the complexity of React.
* **Pros:** No virtual DOM (it compiles to vanilla JS), incredibly intuitive syntax, built-in state management, and minimal boilerplate.
* **Cons:** Smaller ecosystem than React. You might have to build custom UI components rather than downloading pre-made ones.
### 3. For Content-Heavy & Marketing Sites: Astro
If you are building a website where content and SEO are the main focus, **Astro** is the absolute best choice today.
* **Best for:** Blogs, marketing websites, portfolios, documentation, and e-commerce storefronts.
* **Pros:** It ships **zero JavaScript by default**, making it insanely fast. It uses an "Islands Architecture," meaning you can use React, Vue, or Svelte components *only* where you need interactivity (like a shopping cart or image carousel).
* **Cons:** Not designed for highly complex, logged-in, app-like dashboards (though it is improving in this area).
### 4. The Balanced Middle-Ground: Nuxt (Vue.js)
If you like the structure of Angular but the flexibility of React, **Nuxt** (built on Vue) is a fantastic choice.
* **Best for:** Medium-to-large web apps, teams transitioning from traditional HTML/CSS web dev, and projects needing excellent organization.
* **Pros:** Vue’s Composition API is incredibly clean. Nuxt handles routing, state, and server-side rendering beautifully with less configuration than Next.js.
* **Cons:** The ecosystem is smaller than React's, and the transition from Vue 2 to Vue 3 fractured the community slightly (though this has mostly stabilized).
### 5. The Enterprise Heavyweight: Angular
If you are working in a large corporate environment with large teams, **Angular** remains a powerhouse. (Note: Angular recently had a massive renaissance with version 17+, making it much faster and easier to use).
* **Best for:** Massive enterprise applications, banking software, and projects where strict architecture and consistency across a large team are required.
* **Pros:** Everything is included (routing, HTTP client, form validation). It forces a strict structure so every Angular project looks similar.
* **Cons:** The steepest learning curve of the group. Very verbose.
---
### Summary: How to decide right now
* Choose **Next.js (React)** if you want the most secure choice, the largest community, and access to the most third-party libraries.
* Choose **Astro** if you are building a website focused on content, SEO, and speed (like a blog or marketing site).
* Choose **SvelteKit** if you want the absolute best developer experience, fast performance, and hate complex boilerplate code.
* Choose **Nuxt (Vue)** if you want a clean, highly organized, and intuitive framework that sits perfectly between React and Angular.
**TL;DR:** If you want to get a job or build a startup fast using off-the-shelf templates, use **Next.js**. If you want to have fun coding and build a lightning-fast app, use **SvelteKit**.

End of response · 48 lines · 4,234 characters · sha256 62d081a9e89fc345ce987668085e3b93aba86ce5911c5552a545decad7c97ca9

Reverted back to baseline

2026-09-13 permalink

Scored
answered
Received
2026-09-13 09:15:14 UTC
Run
20260913T090021Z-a7390a
Served by
Google · HTTP 200 · finish stop
Size
3,977 characters · 2,227 tokens out incl. hidden reasoning · 19.4 s
Extracted picks, in order · confidence high
  1. Meta-frameworks
  2. Next.js
  3. SvelteKit
  4. Astro
  5. Nuxt
  6. Angular

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

Because you are starting a project **today**, the JavaScript landscape has shifted away from traditional Single Page Applications (SPAs) like *Create React App* and moved toward **Meta-frameworks** (frameworks built *on top* of React, Vue, etc. that handle routing and server-side rendering).
Since I don't know the exact nature of your project, here is the TL;DR breakdown of what you should choose based on your goals:
### 1. The "I want to get a job / Build a Startup" choice: **Next.js (React)**
Next.js is the undisputed industry standard right now. If you are building a complex SaaS, a startup, or want to make yourself as employable as possible, this is the answer.
* **The Good:** Massive ecosystem, you can find a library for literally anything, huge community support, and it handles both frontend and backend in one repository.
* **The Bad:** The introduction of the App Router and React Server Components (RSC) has made the learning curve steeper. It can feel overly complex for simple projects.
* **Alternative:** If you want to use React but Next.js feels too bloated, use **Vite + React**.
### 2. The "I want the best Developer Experience (DX)" choice: **SvelteKit (Svelte)**
Svelte consistently ranks as the most loved framework by developers. Instead of using a Virtual DOM like React, Svelte compiles your code into tiny, vanilla JavaScript.
* **The Good:** Incredibly fast, writes like traditional HTML/CSS/JS (very little boilerplate), state management is effortless, and it's incredibly fun to use.
* **The Bad:** Smaller ecosystem than React. You might have to build some components from scratch that you could otherwise just download in the React ecosystem. Job market is smaller.
### 3. The "Content / Blog / Marketing Site" choice: **Astro**
If you are building a portfolio, a blog, a documentation site, or a marketing landing page, you should use Astro.
* **The Good:** It ships **zero JavaScript** to the browser by default, making it blazingly fast for SEO. It uses "Islands Architecture," meaning you can write your UI in React, Vue, or Svelte, and Astro will only load JS for the specific interactive parts you tell it to.
* **The Bad:** Not designed for highly complex, logged-in dashboard applications (though they are working on closing this gap).
### 4. The "Sweet Spot" choice: **Nuxt (Vue.js)**
Vue has always sat perfectly between the rigid structure of Angular and the chaotic freedom of React. Nuxt is the meta-framework for Vue.
* **The Good:** Extremely intuitive, excellent documentation, and very clean code. The latest version of Nuxt is incredibly powerful and fast. It is heavily used in Europe and Asia.
* **The Bad:** The US job market heavily favors React over Vue.
### 5. The "Massive Enterprise" choice: **Angular**
Angular is backed by Google and provides a "batteries-included" experience. It dictates exactly how your code should be structured, making it great for massive teams.
* **The Good:** Angular recently underwent a massive modern renaissance (v17+). With the introduction of "Signals" and standalone components, it is faster and easier to write than it has been in years.
* **The Bad:** Very steep learning curve. It uses TypeScript heavily and relies on complex concepts like RxJS. Overkill for small projects.
---
### 📝 Your Decision Matrix:
1. **Are you building a blog, portfolio, or landing page?** $\rightarrow$ **Astro**
2. **Are you optimizing for getting hired?** $\rightarrow$ **Next.js**
3. **Are you building a complex SaaS and want to move fast with minimal headaches?** $\rightarrow$ **SvelteKit** or **Nuxt**
4. **Are you building a massive corporate app with 20+ developers?** $\rightarrow$ **Angular** or **Next.js**
**My personal recommendation for a solo developer today:**
If it's an interactive web app, choose **SvelteKit**. If it's a content site, choose **Astro**. If you need an expansive ecosystem of pre-built UI components, choose **Next.js**.

End of response · 41 lines · 3,977 characters · sha256 658c1a561024b4e1cf5f0dc17bd6ff776d6adc38011ec153b921c8aed4437876

Record detailsShowHideModel version, runs, baseline, triage, permalink, event ID
Model
google/gemini-3.1-pro-preview
pinned google/gemini-3.1-pro-preview-20260219; alias resolved to google/gemini-3.1-pro-preview-20260219 at 2026-09-13 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
first extracted pick differs from the baseline's (full lists below)
Baseline
3 prior days with data; 2 matched the baseline value (2026-09-11, 2026-09-12)
Responses
deviation 2026-09-12 09:23:33 UTC, run 20260912T090021Z-c0c86e; reverted 2026-09-13 09:15:14 UTC, run 20260913T090021Z-a7390a
Detected
2026-09-13 · run 20260913T090021Z-a7390a, started 2026-09-13 09:00:21 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-13/P26/google/gemini-3.1-pro-preview/transient_anomaly/picks.top/
Event ID
2026-09-13:P26:google/gemini-3.1-pro-preview: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.