coder
Newbie
Moderator

Vue 3 has been out for several years now, so why does it still feel like so few people are using it?

As the title suggests, Vue 3 has evolved from the Vue@next version in 2019 to its current 3.2 iteration, spanning over three years. It seems that Vue 2 remains more prevalent in the frontend community. On platforms like JuDan, most frontend developers still prioritize Vue 2 when starting new projects. What factors drive this preference?

five
Newbie
1#

Last week, out of boredom, I migrated a company project from Vue2/webpack to Vue3/Rspack in the preview environment. Three months ago, after confirming that `<script setup>` was already very stable in Vue2, I spent half a month refactoring it over. This time, aside from writing a polyfill for dynamically setting reactive fields where needed, the transition was nearly painless. My takeaway is this: despite differing architecture and reactive principles, the API gap between Vue2 and Vue3 isn't significant—many Vue3 projects still revolve around Options. This leads to two outcomes: first, the switching cost is low; second, the switching benefits are also modest.



see
Newbie
2#

If my framework is Vue 2, I'll stick with Vue 2. If it's Vue 3, I'll write Vue 3 using Vue 2 syntax. If you think Vue 3 is so great, feel free to comment with a scenario where Vue 3 is unbeatable and Vue 2 is utterly useless. But if you absolutely insist on using Vue 3, I can't help but ask: Why should I use Vue 3? What additional problems does it solve for me?


This is what I asked the AI; let's go through them one by one.

Reactive System: Nothing particularly stands out.

Bundle Size: Useful, but given current network conditions, it's not a concern.

Compilation Optimization: Useful, but the difference isn't groundbreaking—not a priority.

Code Organization: Unfamiliar and annoying.

TypeScript Support: Useful, but I don't use it.

New features: Haven't used them. They're probably great, but I haven't encountered issues that require them.

Custom directives: There's a difference, but I don't feel it's better.

Lifecycles: There's a difference, but I don't feel it's better.

Filters: There's a difference, but I don't feel it's better.



Bottom line: still no compelling reason to switch.

New features: haven't encountered any Vue 2 limitations that absolutely require Vue 3's new features.

Performance improvements exist, but honestly—slower startup or build times in frontend? Who cares? As long as hot reloading is fast.

4MB vs. 6MB post-build? With today's internet speeds? Not a concern.






Login
{{error.username}}
{{error.password}}
or
Register
{{error.username}}
{{error.nickname}}
{{error.email}}
{{error.password}}
{{error.repassword}}
Forget the password
{{error.email}}
{{error.code}}
Reply:{{reply.touser}}
Edit
Allow cookies on this browser?

All cookies currently used by FreeTalkHub are strictly necessary. Our cookies are employed for login authentication purposes and utilise Google's one-click login functionality, serving no other purpose.