October 6, 2026•5 min read

State of JS 2025 Says Developers Use Only 2.6 Frameworks in a Whole Career

Try counting every framework you have ever touched, then cut the list down to what you actually used for work. It comes out far shorter than you would guess. State of JS 2025 asked 13,002 developers, and the average is only 2.6.

Read in Indonesian

Try to imagine being asked to write down every technology you have ever tried. Framework A, library B, build tool C, plus a tool or two you only opened a tutorial for. That list usually gets very long. But cut it down to what you actually used for work, and the contents are far shorter than you expect. 🤔

Well, State of JS 2025 happens to have a number that proves exactly this.

Key takeaways

State of JS 2025 recorded that the average developer has only ever used 2.6 front-end frameworks over a whole career, and around 97% of respondents stopped at 6 or fewer. That small number is not laziness; technology choices at work are team decisions, not personal ones. What changes every few years is only the names and the APIs, while reading an error and breaking a problem apart stay the same. On the CSS side, State of CSS 2025 shows a similar pattern: 27% of respondents use no CSS framework at all.

How many frameworks do we actually use?

According to the State of JS 2025 survey (Devographics, closed 11 Nov 2025, with 13,002 respondents), the average respondent has only ever used 2.6 front-end frameworks over a career. You can check the source directly on the State of JS 2025 front-end frameworks page.

An average alone is sometimes not enough, so let's look at the distribution:

Number of frameworks Respondents
0 1,135
1 2,444
2 3,436
3 2,859
4 1,541
5 824
6 395
7 218
8 82
9 42
10 18
11 8

The peak sits at 2 frameworks, with 3,436 respondents. After that the numbers fall off quickly. Around 97% of respondents have used 6 frameworks or fewer, while those who ever touched 7 or more are only about 2.8%.

The survey also writes that the ecosystem has stabilized. Almost no new front-end frameworks showed up this year, and the "newcomer" Svelte is 9 years old. So the JavaScript world that supposedly swaps frameworks every week is more meme than reality. 😄

And how does that compare to my own history?

My own learning history turns out to sit close to that pattern, even though the list of things I have touched is a bit longer. I first learned front-end with Angular, back in school. The reason was simple: plenty of tutorials online covered Angular, mostly from The Net Ninja. Then React, still in school, in the class component era.

After that I moved to Vue to be anti-mainstream, to differ from friends who used React. Then Nuxt 2 because the people around me used Next, again to stand apart. I tried Svelte for a while, then migrated to Nuxt 3, and now Nuxt 4.

I also tried TanStack and Astro, but got stuck reading the how-to guide. Neither became a real project. So if you count honestly, the ones actually used are just those.

CSS was more winding. I used to be proud of indent-based SASS, because it felt cooler, while plain CSS or SCSS felt meh. Then Bootstrap, Tailwind, briefly PicoCSS out of curiosity, then back to Tailwind. Over time I realized PostCSS was enough, and now I am back to plain CSS because there is less bloat.

It turns out I am not alone. In State of CSS 2025, of 3,977 respondents who answered the CSS framework question, 1,061 people (around 27%) use no CSS framework at all. For comparison, Tailwind is used by 2,041 people (≈51%) and Bootstrap by 1,194 people (≈30%). For preprocessors, Sass/SCSS is used by 2,434 people (≈61%), PostCSS by 1,517 people (≈38%), and 838 people (≈21%) use none at all.

Why is the number so small?

The answer is not that developers are lazy about learning. At work, a framework is a team decision, not a personal one. You cannot swap the stack overnight out of curiosity while a teammate has to maintain that code with you.

The cost of switching is very real too. You have to find replacements for a whole library ecosystem, reset your tooling, and find people who can review your code. Switching a framework is like moving house: the stuff is the same, but everything has to be repacked, and you need time to learn where the light switches are. 📦

The survey data also shows something interesting about Solid. Only around 10% of respondents use it, but it has the highest satisfaction five years running. So the most liked tool is not necessarily the most used. The most common complaints in the survey were React issues, over-complication, performance, state management, and choice overload. Too many options really are tiring, like opening a restaurant menu as thick as a thesis.

Count yours first, how many have you used?

Before you read on, grab paper or open your notes. Write down every front-end framework you have ever used. Only count the ones that actually built something, not the ones that stopped on day one of a tutorial.

Done? Now compare with the table above. If you land on 2 or 3, you are at the peak of the curve. If you are at 7 or more, you are in that 2.8% group. Neither is wrong; this is just a small mirror for checking your own expectations. 🪞

What changes and what doesn't

Every few years, only the names, the APIs, and the conventions change. Class components before, functions now. Options API before, composition now. The syntax moves, but the problems being solved are nearly the same.

What does not change matters more: how you read an error, how you shrink a problem until you find its cause, and how you think about data and system boundaries. No wonder the first day on a new framework usually feels familiar. The error messages differ, but the way you read them does not.

So what are the practical consequences?

First, the learning list can be shortened. There is no obligation to try everything trending on your timeline. Second, dig deeper into what you already use. Understanding reactivity, routing, and rendering in one framework is usually more useful than knowing five frameworks at the surface.

Third, measure yourself by things that are portable. HTTP, core JavaScript, CSS, debugging, and data design travel with you, while framework syntax may not.

When does learning something new still make sense? When your project genuinely hits a problem current tools cannot solve, when the team agrees to switch, or when you have a real project to try it on rather than a how-to guide. 😅

As for my own history, after the run of Angular, React, Vue, Nuxt, and Svelte, the current job is all vanilla. No framework at all. In the end, that long journey led back to the plainest starting point. 😭

Get better at shipping code.

Join the other developers getting tech updates, tips, and relaxed tutorials in their inbox every week.

Stay in the loop

Tech updates, coding tips, and relaxed insights straight to your inbox every week.

No spam. Unsubscribe anytime.

Read next

See all
KarierWhen You Pick a Framework Just to Look Different

The last time you chose a new framework or library, was it because your problem needed that tool, or because it sounded cool and few people around you were using it? That question is uncomfortable. Technology decisions are often made for reasons that never appear in any technical document.

For developers who learn by struggling

© 2026 Inva.dev.