MODELDRIFT.WATCH

Sep 16 · Day 7

MINOR · GEMINI · QUESTION 31

Gemini 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 15beforePermalink

Picks read from the answer, in order
  1. React
  2. Svelte
  3. Vue.js
  4. Astro
  5. Angular

Because you didn't specify what you are building, your experience level, or your end goal, there is no single "best" answer. However, the JavaScript ecosystem has stabilized a lot recently.

Today, the standard practice is to choose a meta-framework (which handles routing, server-side rendering, and performance) rather than just a UI library.

Here is the breakdown of which framework you should choose in 2024 based on your specific needs:


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

If you want to get a job, build a SaaS, or want the guarantee that there is a library/package for everything, choose React—specifically using the Next.js framework.

  • •Why choose it: It has the largest ecosystem, the most community support, and accounts for the vast majority of developer jobs. If you run into a bug, someone has already solved it on StackOverflow. It also translates well to mobile app development via React Native.
  • •The Catch: React introduces complex concepts (like hooks, dependency arrays, and Server Components). It is arguably the hardest of the top three to master, and the ecosystem changes frequently.

2. The Best Developer Experience: Svelte (SvelteKit)

If you are building a personal project, a startup where you control the tech stack, or you just want to enjoy coding, choose SvelteKit.

  • •Why choose it: Svelte consistently ranks as the "most loved" framework by developers. It compiles away to vanilla JavaScript (no virtual DOM), making it blazing fast. You write significantly less code than in React, and it feels much closer to writing standard HTML, CSS, and JS.
  • •The Catch: The job market for Svelte is much smaller than React or Angular. The ecosystem of third-party UI libraries is also smaller.

3. The Best Middle-Ground: Vue.js (Nuxt.js)

If you want something easier to learn than React, but with a larger ecosystem and job market than Svelte, choose Nuxt.js (built on Vue).

  • •Why choose it: Vue is famous for having the best, most readable documentation in the industry. It provides a clean separation of HTML, CSS, and JS within a single file. It is incredibly popular in Europe and parts of Asia, and is an excellent choice for a wide variety of apps.
  • •The Catch: It is the "middle child." It doesn't have the sheer corporate dominance of React, nor the ultra-hype of Svelte.

4. For Content, Blogs, and Marketing Sites: Astro

If you are building a website where the main focus is reading content (a blog, a portfolio, a company landing page, an e-commerce storefront), choose Astro.

  • •Why choose it: Astro ships zero JavaScript to the browser by default, making your websites incredibly fast. If you need an interactive element (like a search bar or an image carousel), Astro's "Islands" architecture allows you to plug in components from React, Svelte, or Vue seamlessly.
  • •The Catch: It is not designed for highly interactive, dashboard-style web applications (like Spotify or a CRM).

5. For Large Enterprise Teams: Angular

If you are working in a massive corporate environment, or building an app with dozens of other developers, choose Angular.

  • •Why choose it: Backed by Google, Angular is "batteries included." It comes with routing, form validation, and HTTP clients built-in. It enforces strict rules and requires TypeScript, which prevents large teams from making messy codebases.
  • •The Catch: It has a massive learning curve, feels very verbose, and is generally overkill for solo developers or small startups.

Summary: Which should you pick?

  • •Pick React (Next.js) if: You want a job, or you are building a complex SaaS and need pre-built components for everything.
  • •Pick SvelteKit if: You want to build a web app incredibly fast and actually enjoy the process.
  • •Pick Astro if: You are building a blog, portfolio, or static website.
  • •Pick Vue (Nuxt) if: You want an elegant, easy-to-learn alternative to React with a solid ecosystem.

SEP 16afterPermalink

Picks read from the answer, in order
  1. Next.js
  2. Astro
  3. SvelteKit or Nuxt
  4. HTMX + Alpine.js
  5. Mobile First Expo

Because the JavaScript ecosystem moves so quickly, the right choice depends entirely on what you are building and your goals.

However, if you want the short answer:

  • •The Industry Default: Use Next.js (React).
  • •For Fast, Content-Heavy Sites: Use Astro.
  • •For the Best Developer Experience: Use SvelteKit or Nuxt (Vue).

Here is a breakdown of which framework to choose based on your specific project needs today.


1. The "Safe" Industry Default: Next.js (React)

Today, you generally shouldn't start a raw React project from scratch; you should use a "meta-framework." Next.js is the undisputed king of the React ecosystem right now.

  • •Best for: SaaS products, complex dashboards, e-commerce, and enterprise applications.
  • •Pros: The largest ecosystem, easiest to find solutions on StackOverflow, massive job market, and excellent support for Server-Side Rendering (SSR) and API routes.
  • •Cons: The new "App Router" has a steep learning curve, and it can be overkill (and heavily reliant on Vercel) for simple projects.
  • •Alternative: If you just want a simple React Single Page Application (SPA) without server-side rendering, use React + Vite (Do not use Create React App, it is deprecated).

2. The Speed Demon: Astro

If your site is mostly content (meaning users read it more than they click complex interactive buttons), Astro is currently the best tool on the market.

  • •Best for: Blogs, marketing websites, portfolios, documentation, and SEO-heavy storefronts.
  • •Pros: It ships zero JavaScript to the browser by default, making it blazingly fast. It uses an "Islands Architecture," meaning you can drop in interactive React, Vue, or Svelte components only where you need them (like a shopping cart or search bar).
  • •Cons: Not meant for highly interactive, app-like experiences (like Spotify or Gmail).

3. The Developer Experience (DX) Champions: SvelteKit or Nuxt

Many developers suffer from "React fatigue" due to its complex state management and rendering quirks. Svelte and Vue offer a much more enjoyable, intuitive coding experience.

  • •SvelteKit (Svelte): Compiles away the framework, resulting in tiny bundle sizes. It has no virtual DOM and the syntax is incredibly clean. It is highly loved by indie developers.
  • •Nuxt (Vue): Vue strikes a perfect balance between React's power and Svelte's simplicity. Nuxt is a mature, incredibly well-documented framework for building full-stack Vue apps.
  • •Best for: Solo developers, small teams, and startups who want to move incredibly fast and enjoy writing code.
  • •Cons: Smaller job markets and slightly fewer third-party libraries compared to React.

4. The Anti-Framework Trend: HTMX + Alpine.js

There is a massive movement right now moving away from heavy JavaScript frontend frameworks altogether.

  • •Best for: Developers who love backend languages (Python/Django, Ruby on Rails, PHP/Laravel, Go) and want to keep state on the server.
  • •Pros: You write HTML attributes instead of JavaScript. It makes your frontend incredibly simple and lightweight while still giving you a modern, SPA-like feel (dynamic content loading without page refreshes).
  • •Cons: Requires a traditional backend server; not suitable if you want to build a decoupled frontend/backend.

5. Mobile First: Expo (React Native)

If your primary goal is to launch an iOS and Android app (with a web version as a secondary bonus), you should look at Expo.

  • •Best for: Cross-platform mobile apps.
  • •Pros: Expo has matured incredibly well. You write React, and it compiles to native mobile code. The new Expo Router brings web-like file-based routing to mobile apps.

Summary Decision Matrix:

  • 1.I want to get a job or hire developers easily: Next.js (React)
  • 2.I am building a blog or marketing site: Astro
  • 3.I am building a complex SaaS or Web App: Next.js or Nuxt
  • 4.I want the most fun/elegant coding experience: SvelteKit
  • 5.I am a backend dev who hates writing JavaScript: HTMX
Exact recordShowHideEach response verbatim, unrendered, with line numbers and its sha256

Before baseline

2026-09-15 permalink

Scored
answered
Received
2026-09-15 09:24:33 UTC
Run
20260915T090004Z-599f39
Served by
Google · HTTP 200 · finish stop
Size
4,052 characters · 2,083 tokens out incl. hidden reasoning · 17.5 s
Extracted picks, in order · confidence high
  1. React
  2. Svelte
  3. Vue.js
  4. Astro
  5. Angular

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

Because you didn't specify what you are building, your experience level, or your end goal, there is no single "best" answer. However, the JavaScript ecosystem has stabilized a lot recently.
Today, the standard practice is to choose a **meta-framework** (which handles routing, server-side rendering, and performance) rather than just a UI library.
Here is the breakdown of which framework you should choose in 2024 based on your specific needs:
---
### 1. The "Safe Bet" & Industry Standard: **React (Next.js)**
If you want to get a job, build a SaaS, or want the guarantee that there is a library/package for *everything*, choose React—specifically using the **Next.js** framework.
* **Why choose it:** It has the largest ecosystem, the most community support, and accounts for the vast majority of developer jobs. If you run into a bug, someone has already solved it on StackOverflow. It also translates well to mobile app development via React Native.
* **The Catch:** React introduces complex concepts (like hooks, dependency arrays, and Server Components). It is arguably the hardest of the top three to master, and the ecosystem changes frequently.
### 2. The Best Developer Experience: **Svelte (SvelteKit)**
If you are building a personal project, a startup where you control the tech stack, or you just want to enjoy coding, choose **SvelteKit**.
* **Why choose it:** Svelte consistently ranks as the "most loved" framework by developers. It compiles away to vanilla JavaScript (no virtual DOM), making it blazing fast. You write significantly less code than in React, and it feels much closer to writing standard HTML, CSS, and JS.
* **The Catch:** The job market for Svelte is much smaller than React or Angular. The ecosystem of third-party UI libraries is also smaller.
### 3. The Best Middle-Ground: **Vue.js (Nuxt.js)**
If you want something easier to learn than React, but with a larger ecosystem and job market than Svelte, choose **Nuxt.js** (built on Vue).
* **Why choose it:** Vue is famous for having the best, most readable documentation in the industry. It provides a clean separation of HTML, CSS, and JS within a single file. It is incredibly popular in Europe and parts of Asia, and is an excellent choice for a wide variety of apps.
* **The Catch:** It is the "middle child." It doesn't have the sheer corporate dominance of React, nor the ultra-hype of Svelte.
### 4. For Content, Blogs, and Marketing Sites: **Astro**
If you are building a website where the main focus is *reading content* (a blog, a portfolio, a company landing page, an e-commerce storefront), choose **Astro**.
* **Why choose it:** Astro ships **zero JavaScript to the browser by default**, making your websites incredibly fast. If you need an interactive element (like a search bar or an image carousel), Astro's "Islands" architecture allows you to plug in components from React, Svelte, or Vue seamlessly.
* **The Catch:** It is not designed for highly interactive, dashboard-style web applications (like Spotify or a CRM).
### 5. For Large Enterprise Teams: **Angular**
If you are working in a massive corporate environment, or building an app with dozens of other developers, choose **Angular**.
* **Why choose it:** Backed by Google, Angular is "batteries included." It comes with routing, form validation, and HTTP clients built-in. It enforces strict rules and requires TypeScript, which prevents large teams from making messy codebases.
* **The Catch:** It has a massive learning curve, feels very verbose, and is generally overkill for solo developers or small startups.
---
### Summary: Which should you pick?
* **Pick React (Next.js) if:** You want a job, or you are building a complex SaaS and need pre-built components for everything.
* **Pick SvelteKit if:** You want to build a web app incredibly fast and actually enjoy the process.
* **Pick Astro if:** You are building a blog, portfolio, or static website.
* **Pick Vue (Nuxt) if:** You want an elegant, easy-to-learn alternative to React with a solid ecosystem.

End of response · 41 lines · 4,052 characters · sha256 39881f6c210c762a705b361a54023354a813aff54d93227b2e74e91747785533

After this run

2026-09-16 permalink

Scored
answered
Received
2026-09-16 09:24:50 UTC
Run
20260916T090004Z-fdcf7b
Served by
Google · HTTP 200 · finish stop
Size
4,120 characters · 2,138 tokens out incl. hidden reasoning · 20.0 s
Extracted picks, in order · confidence high
  1. Next.js
  2. Astro
  3. SvelteKit or Nuxt
  4. HTMX + Alpine.js
  5. Mobile First Expo

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

Because the JavaScript ecosystem moves so quickly, the right choice depends entirely on **what you are building** and **your goals**.
However, if you want the short answer:
* **The Industry Default:** Use **Next.js (React)**.
* **For Fast, Content-Heavy Sites:** Use **Astro**.
* **For the Best Developer Experience:** Use **SvelteKit** or **Nuxt (Vue)**.
Here is a breakdown of which framework to choose based on your specific project needs today.
---
### 1. The "Safe" Industry Default: Next.js (React)
Today, you generally shouldn't start a raw React project from scratch; you should use a "meta-framework." **Next.js** is the undisputed king of the React ecosystem right now.
* **Best for:** SaaS products, complex dashboards, e-commerce, and enterprise applications.
* **Pros:** The largest ecosystem, easiest to find solutions on StackOverflow, massive job market, and excellent support for Server-Side Rendering (SSR) and API routes.
* **Cons:** The new "App Router" has a steep learning curve, and it can be overkill (and heavily reliant on Vercel) for simple projects.
* *Alternative:* If you just want a simple React Single Page Application (SPA) without server-side rendering, use **React + Vite** (Do not use Create React App, it is deprecated).
### 2. The Speed Demon: Astro
If your site is mostly content (meaning users read it more than they click complex interactive buttons), Astro is currently the best tool on the market.
* **Best for:** Blogs, marketing websites, portfolios, documentation, and SEO-heavy storefronts.
* **Pros:** It ships **zero JavaScript** to the browser by default, making it blazingly fast. It uses an "Islands Architecture," meaning you can drop in interactive React, Vue, or Svelte components *only* where you need them (like a shopping cart or search bar).
* **Cons:** Not meant for highly interactive, app-like experiences (like Spotify or Gmail).
### 3. The Developer Experience (DX) Champions: SvelteKit or Nuxt
Many developers suffer from "React fatigue" due to its complex state management and rendering quirks. Svelte and Vue offer a much more enjoyable, intuitive coding experience.
* **SvelteKit (Svelte):** Compiles away the framework, resulting in tiny bundle sizes. It has no virtual DOM and the syntax is incredibly clean. It is highly loved by indie developers.
* **Nuxt (Vue):** Vue strikes a perfect balance between React's power and Svelte's simplicity. Nuxt is a mature, incredibly well-documented framework for building full-stack Vue apps.
* **Best for:** Solo developers, small teams, and startups who want to move incredibly fast and enjoy writing code.
* **Cons:** Smaller job markets and slightly fewer third-party libraries compared to React.
### 4. The Anti-Framework Trend: HTMX + Alpine.js
There is a massive movement right now moving *away* from heavy JavaScript frontend frameworks altogether.
* **Best for:** Developers who love backend languages (Python/Django, Ruby on Rails, PHP/Laravel, Go) and want to keep state on the server.
* **Pros:** You write HTML attributes instead of JavaScript. It makes your frontend incredibly simple and lightweight while still giving you a modern, SPA-like feel (dynamic content loading without page refreshes).
* **Cons:** Requires a traditional backend server; not suitable if you want to build a decoupled frontend/backend.
### 5. Mobile First: Expo (React Native)
If your primary goal is to launch an iOS and Android app (with a web version as a secondary bonus), you should look at Expo.
* **Best for:** Cross-platform mobile apps.
* **Pros:** Expo has matured incredibly well. You write React, and it compiles to native mobile code. The new Expo Router brings web-like file-based routing to mobile apps.
---
### Summary Decision Matrix:
1. **I want to get a job or hire developers easily:** Next.js (React)
2. **I am building a blog or marketing site:** Astro
3. **I am building a complex SaaS or Web App:** Next.js or Nuxt
4. **I want the most fun/elegant coding experience:** SvelteKit
5. **I am a backend dev who hates writing JavaScript:** HTMX

End of response · 50 lines · 4,120 characters · sha256 015e775160db5e5ecceb20e42efc64ac3e01d2b7e3ff1feaaa0522155471b647

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-16 09:00:03 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-10, 2026-09-14, 2026-09-15)
Responses
before 2026-09-15 09:24:33 UTC, run 20260915T090004Z-599f39; after 2026-09-16 09:24:50 UTC, run 20260916T090004Z-fdcf7b
Detected
2026-09-16 · run 20260916T090004Z-fdcf7b, started 2026-09-16 09:00:04 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-16/P26/google/gemini-3.1-pro-preview/pick_change/picks.top/
Event ID
2026-09-16:P26:google/gemini-3.1-pro-preview: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.