modeldrift.watchA daily record of AI model behavior. All times UTC.

Observation period — public launch soon. The record below is real and updated daily.

Significant Top-pick change·recommendation·2026-09-11

Gemini 3.1 Pro Preview gives a different first recommendation (as extracted).

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-11 09:00:01 UTC (matches the pin)
Prompt
P26 (recommendation)
Change
first extracted pick differs from the baseline's (full lists below)
Baseline
1 prior day with data; 1 matched the baseline value (2026-09-10)
Detected
2026-09-11 · run 20260911T090002Z-da0dd3 (2026-09-11 09:00:02 UTC) · scorer v1
Severity
significant — rule: a change of the #1 pick is significant
Event ID
2026-09-11:P26:google/gemini-3.1-pro-preview:pick_change:picks.top
Permalink
https://modeldrift.watch/e/2026-09-11/P26/google/gemini-3.1-pro-preview/pick_change/picks.top/
Prompt P26sent verbatim
Which JavaScript framework should I start a new project with today?

Why this prompt Training-cutoff lag detector.

Before baseline

2026-09-10

Scored
answered
Received
2026-09-10 22:34:07 UTC
Run
20260910T221001Z-bb5bd1
Served by
Google · finish stop
Size
4,590 characters · 2,295 tokens out incl. hidden reasoning · 19.6 s
Extracted picks, in order · confidence high
  1. React
  2. Vue.js
  3. Svelte
  4. Angular
  5. Astro

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

The "best" JavaScript framework to start a project with today depends heavily on what you are building, your experience level, and your goals (e.g., getting a job vs. building a startup).
However, in modern web development, **you rarely start with just a framework anymore; you start with a "meta-framework"** (a framework built on top of a library to handle routing, server-side rendering, and API creation).
Here is the breakdown of the best choices today based on your specific needs:
---
### 1. The Safest Default: React (via Next.js)
If you aren't sure what to pick, pick this. React is the undisputed industry standard. Today, the recommended way to build a React application is by using **Next.js**.
* **Best for:** Almost anything (SaaS, e-commerce, dashboards), finding a job, finding third-party libraries, and getting help on StackOverflow/ChatGPT.
* **Pros:** Massive ecosystem, heavily backed by Vercel, introduces cutting-edge features (like React Server Components).
* **Cons:** The ecosystem changes rapidly (the recent shift to the Next.js "App Router" has been polarizing and complex), and it can be overkill for simple websites.
* **Alternative:** If you just want a simple React Single Page App (SPA) without a backend, use **Vite + React**. *(Do not use Create React App; it is deprecated).*
### 2. The Developer Experience Champion: Vue.js (via Nuxt 3)
Vue hits the perfect sweet spot between React’s wild-west flexibility and Angular’s strict rules. It is incredibly intuitive.
* **Best for:** Developers who want a clean, logical syntax, excellent documentation, and rapid development speed.
* **Pros:** Much less boilerplate than React. Its reactivity system makes state management incredibly easy. **Nuxt 3** is highly polished and arguably offers a better out-of-the-box developer experience than Next.js.
* **Cons:** The job market in the US is smaller than React (though it is massive in Europe and Asia).
### 3. The Performance & Simplicity King: Svelte (via SvelteKit)
Svelte takes a different approach: it compiles your code into tiny, vanilla JavaScript files rather than using a heavy "virtual DOM" in the browser.
* **Best for:** Highly interactive apps where performance and bundle size matter, and developers who are tired of complex framework rules.
* **Pros:** Writing Svelte feels like writing pure HTML, CSS, and JS. It requires almost zero boilerplate. It consistently ranks as the "most loved" framework in developer surveys.
* **Cons:** Smaller ecosystem. You might have to build custom UI components because there aren't as many pre-built libraries as there are for React.
### 4. The Enterprise Behemoth: Angular
Backed by Google, Angular is a "batteries-included" framework. It dictates exactly how you should structure your code, handle forms, and make HTTP requests.
* **Best for:** Large enterprise companies, massive development teams, and complex internal dashboards.
* **Pros:** Highly opinionated (which prevents messy code in large teams), uses TypeScript by default. **Note:** Angular recently released v17/v18, which modernized the framework immensely (introducing "Signals" and standalone components), making it much faster and easier to use than it used to be.
* **Cons:** A very steep learning curve. It feels very "heavy" if you are building a small project.
### 5. The Content Heavyweight: Astro
Astro is a unique framework designed specifically for content-driven websites. It ships **zero JavaScript to the browser by default**, making websites blazing fast.
* **Best for:** Blogs, documentation sites, portfolios, and marketing websites.
* **Pros:** Unbeatable performance and SEO. The best feature? **You can use React, Vue, or Svelte components inside Astro**.
* **Cons:** Not designed for highly interactive, app-like experiences (like Spotify or a banking dashboard).
---
### Summary: Which should you choose?
* **Want to get hired as fast as possible?** Choose **Next.js (React)**.
* **Building a complex Web App / SaaS quickly?** Choose **Nuxt (Vue)** or **Next.js (React)**.
* **Want the fastest performance and the most fun?** Choose **SvelteKit**.
* **Building a blog, portfolio, or marketing site?** Choose **Astro**.
* **Joining a giant corporate team?** Choose **Angular**.
**My personal recommendation for a new project today:**
If it's a content site, use **Astro**. If it's a web app and you want to move fast with zero headaches, use **Nuxt** or **SvelteKit**. If you want a massive ecosystem and AI tools to write the code for you, use **Next.js**.

End of response · 51 lines · 4,590 characters · sha256 8514814dbed83a35e8e3392c74f213d8232a48ff1826eef87d317f45faf8b96a

After this run

2026-09-11

Scored
answered
Received
2026-09-11 09:29:55 UTC
Run
20260911T090002Z-da0dd3
Served by
Google · finish stop
Size
4,244 characters · 2,215 tokens out incl. hidden reasoning · 19.5 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 the JavaScript ecosystem evolves so quickly, the best answer depends entirely on **what you are building** and **your team's experience**.
In 2024, the industry has largely moved away from pure Single Page Applications (SPAs) like basic React or Vue, and toward **Meta-frameworks** that handle routing, server-side rendering, and performance out of the box.
Here is the breakdown of the best frameworks to start a project with today, based on your use case:
---
### 1. The Industry Standard: **Next.js** (built on React)
If you want the safest bet, the most community support, and the easiest time finding developers or third-party libraries, choose Next.js.
* **Why it’s great:** It has massive corporate backing (Vercel), handles SEO brilliantly via Server-Side Rendering (SSR), and is the undisputed king of the modern enterprise web.
* **The Catch:** The recent shift to the "App Router" and React Server Components has made it more complex with a steeper learning curve.
* **Best for:** SaaS products, large-scale e-commerce, complex dashboards, and projects where you need to hire developers easily.
### 2. The Best Developer Experience: **SvelteKit** (built on Svelte)
If you want to write clean, minimal code without the boilerplate and complexity of React, SvelteKit is arguably the most loved framework by developers right now.
* **Why it’s great:** It doesn't use a Virtual DOM. It compiles your code into highly optimized vanilla JavaScript, making it incredibly fast. The syntax feels like standard HTML, CSS, and JS.
* **The Catch:** The ecosystem and job market are smaller than React's. You might have to build some custom components instead of downloading a pre-built library.
* **Best for:** Highly interactive web apps, startups moving fast, and teams who are tired of React's complexity.
### 3. For Content, Blogs & Marketing: **Astro**
If you are building a website where people consume content rather than a highly interactive web app, Astro is currently the undisputed champion.
* **Why it’s great:** It ships **zero JavaScript** to the browser by default, making it blazingly fast. If you need interactive elements, Astro uses "Islands Architecture," allowing you to drop in React, Vue, or Svelte components only where needed.
* **The Catch:** It is not designed for highly complex, state-heavy web apps (like Spotify or Figma in the browser).
* **Best for:** Portfolios, blogs, documentation sites, e-commerce storefronts, and marketing pages.
### 4. The Balanced Alternative: **Nuxt** (built on Vue)
If you like the power of React but want a cleaner, more opinionated, and organized structure, Vue and Nuxt are fantastic.
* **Why it’s great:** Nuxt 3 is incredibly stable, extremely fast, and has excellent documentation. It provides a great middle-ground between the strictness of Angular and the "wild west" of React.
* **The Catch:** Like Svelte, the ecosystem isn't as massive as React's (though it is larger than Svelte's).
* **Best for:** Teams who want a fantastic developer experience, convention over configuration, and high performance.
### 5. The Enterprise Heavyweight: **Angular** (v17+)
Angular has historically been seen as bloated, but the recent updates (v17 and v18) have sparked a massive renaissance.
* **Why it’s great:** It includes *everything* out of the box (routing, state management, HTTP client). With the introduction of "Signals" and standalone components, it is faster and easier to write than it has been in a decade.
* **The Catch:** It is highly opinionated, heavily reliant on strict TypeScript, and has a steep learning curve.
* **Best for:** Massive enterprise teams, legacy codebases, and highly complex, data-heavy internal tools.
---
### Summary: How to choose right now?
1. **"I just want a fast website/blog with great SEO."** 👉 Choose **Astro**.
2. **"I'm building a startup/SaaS and need an ecosystem with lots of libraries."** 👉 Choose **Next.js**.
3. **"I want to build an app but I hate React's complexity."** 👉 Choose **SvelteKit** or **Nuxt**.
4. **"I have a massive team of Java/C# developers building enterprise software."** 👉 Choose **Angular**.
5. **"I want a React alternative to Next.js that focuses on web standards."** 👉 Choose **Remix**.

End of response · 47 lines · 4,244 characters · sha256 3bf7dc1cace7deb6785dd01c7df289433bcdd1c900e309ef6443b2d8dca55539

Reading this record

Response text is shown exactly as the API returned it, with Markdown left unrendered. Line numbers and highlights are added by this site; highlights come from the same patterns the scorer uses, so they show what the verdict rests on. Each model is asked once per day (k = 1): a single change can be sampling noise, which is why every event links the full responses rather than a summary. How scoring works.