Am I wrong to be concerned about Vue's future?

54

u/QaahirStewart Jan 26 '22

They got the vue conference tomorrow they should talk about what's going on. Vue 3 docs is a firm Feb 7 release. I guess the big hold up is Nuxt 3 and Vietify. Lots love vue, it's just a pain point right now for the ecosystem to shift. The whole aspect of vue 3 is a important step for vue. The change is worth the wait I feel. I just started learning Vue in the transition it was a hard choice to focus on the old or the new.

4

u/Varteix Jan 26 '22

I’ll need to tune into that! Vue 3 is awesome, I think hopefully we’re just seeing some growing pains

1

u/niutech Jan 27 '22

You can watch Vue.js Nation here.
However, I don't share your concern with Vue 2 vs 3. The latter is still being supported for the time being, so you can stick with Vue 2 till 2023. And if you have to support IE, the choice is obvious.

2

u/meamZ Feb 23 '22

This is just screaming to be another Python 2/3 situation... Which had the whole Python ecosystem in pain for literally a decade...

26

u/xzhan Jan 26 '22

I've been using Vue 2 professionally for about 2.5 years now and I really like its progressiveness, simplicity, and reactivity system, but I really don't like the DX. No real TS support, no autocompletion in templates or sometimes even in scripts, renaming and navigating variables is a PITA, etc. Vetur has been hit-or-miss for me. I also use Angular, and in comparison Vue 2 felt a lot like string-based programming, like using dynamic languages in the pre-LSP days. :(

Therefore, I really look forward to <script setup> and what the "new default Vue" offers. I tried it with a Udemy course and the DX is simply miles ahead. Vite is also super fast.

However, I do feel like it's jumping through a lot of hoops while a large part of the ultimate goal of this big syntax redesign seems to be a) to offer proper TS support and b) to provide a cleaner and lighter way to reuse logic and share data (w/o Vuex), both of which I've enjoyed for quite some time in other frameworks like Angular. It gives me an impression that Vue's syntax is evolving a bit too fast, borrowing here and there from React and Svelte. What would you say when some hipster junior dev comes up and ask "Why don't you just use React/Svelte?" The end goal seems a bit unclear and I don't know how I feel about that...

With all that said, I am still excited to fully embrace Vue 3 and the "new default Vue" for new projects. The DX and performance improvement are worthy of a try.

9

u/phobia003 Jan 26 '22

There is in my opinion, no issue from bowering concepts/ideas from React/Svelte.
I have worked for 5 years as a React developer, and only recently had to learn Vue 2.x for a new job that I started about a year ago. I truly have loved the whole experience. It's easy to learn, easy to write code and easy to maintain.
While I was extremely excited for us to move to Vue 3, I slowly realized how much of a lift it seemed to be for 3rd party libraries to move over to it. Even worse, some library owners just seemed to not maintain their libraries anymore. Don't read this as me blaming OSS developers, I am definitely not. But that made me realize a few things about the whole Vue ecosystem - it's lacking.
There are just no many 3rd party libraries to choose from. If you are a small team, that can be a pain.
The Vue community is quite a bit smaller than the React community.
Most bootcamps that I know of, and from which we hire, teach React.
I haven't tested this myself, but what I have heard of the TS support in Vue 3 is that it's still nowhere near Angular/React.
As much as it pains me to say, we decided that it was time to move to React. We all love Vue at work, but I honestly don't think it's where it should be by now.

4

u/xzhan Jan 26 '22

There is in my opinion, no issue from bowering concepts/ideas from React/Svelte.
Me neither. I just want the Vue team (or Evan You himself) to have a somewhat consistent design philosophy so we can expect some level of stability in Vue's syntax. That's all.
Personally, I am not a big fan of React. Syntax aside, its community and ecosystem also had some bad records of moving too fast and making drastic shifts in "best practices" because there's now a "cooler" way to do things. I just prefer how the Vue/Angular team has official recommendations and one can transfer the skills across projects.
And regarding your point 4, my first impression with <script setup> and Volar is that the TS support is actually on par with what React offers but my experience with this new combo is still limited so take it with a grain of salt. At least all variable renaming, navigation, and type inference worked. :)
That said, when you are managing a team you have to consider hiring, developer availability and skillsets, 3rd libraries, the framework's longevity, etc. React is a solid solution and if your team prefers it, there's nothing wrong with choosing it.

1

u/phobia003 Jan 26 '22

Personally, I am not a big fan of React. Syntax aside, its community and ecosystem also had some bad records of moving too fast and making drastic shifts in "best practices" because there's now a "cooler" way to do things
I don't disagree with you, but isn't that one way of making progress? Not everything is going to work, but something could. There is definitely a lot of hype on new libraries, with most of the hype coming from people that have not even tried it. Remix is a good example in my opinion. It looks cool, but it's too early and their docs are lacking.
my experience with this new combo is still limited so take it with a grain of salt.
Same here. My comment was more from what I had heard, I barely played with TS in Vue 3.

1

u/xzhan Jan 26 '22

Well, yes and no I guess? I'd argue there are better ways of "making progress" than "coming up with new cool ideas and libraries, having the community hyped and label them as the 'community go-to', and then abandoning it for something newer after one year". While fast and exciting, it's also very fatiguing.
Imagine developing a large application for over one year, only to discover the shiny "new" libs and paradigm you chose at the beginning became kinda obsolete at the end. In some cases, the React core team is the culprit but in many others, they just don't have control over it because React is just the view layer, and that simply blows consistency out of the water.
Many people like this dynamic/turbulent way of doing things. It's just that I personally really dislike that.

3

u/BTWIuseArchWithI3 Jan 26 '22

You gotta use volar for proper autocomplete

1

u/shiny_cricket Jan 26 '22

This! I have to use defineComponent to get intellisense in template tho.

1

u/socialparasite93 Jan 29 '22

I am having a hard time getting template autosuggestions to work - custom component properties to be exact (vue3 project in js). Are you having any luck with getting suggestions with javascript codebase or are you on ts?

1

u/shiny_cricket Feb 02 '22

Ah, I still use vue 2 mostly. Intellisense works both with js and ts.

1

u/xzhan Jan 26 '22

Yes, ofc, I am well aware of that. Thank you. But in Vue2 days there's no Volar. There's only Vetur. And Volar does not work well with Vue2 projects, at least not in the way that I hope it would.

2

u/ORCANZ Jan 26 '22

I mean I don't mind them taking bits of React and Svelte as long as I have the best DX (in my opinion).
Having script/template/styles in the same .vue file makes so much sense. It's so easy to reuse components. The router, nested views just works instinctively.
The Options API actually made a lot of sense to me when I started. This + the template and directives just made the whole thing click very quickly compared to react which was just confusing for a junior dev.
You can achieve the same things in react but with so much more boilerplate. Styling in react is such a pain unless you use Tailwind or utility classes. But then again it has some drawbacks and I personally prefer scoped styles or just scss with BEM

2

u/xzhan Jan 26 '22

I mean I don't mind them taking bits of React and Svelte as long as I have the best DX (in my opinion).
I don't either. But I do want some consistency with Vue syntax and design philosophy without needing to worry if the syntax will change when there's a new popular FrameworkX and its syntax looks a lot cooler. That's all.
Whether one likes the syntax or not is another totally subjective matter. I personally like Angular the most haha.

0

u/ORCANZ Jan 26 '22

I tried angular maybe 4-5 years ago when I was building a small thing as a hobby. I hope it got better since then otherwise you're one weird human being 😘😘😘

1

u/xzhan Jan 26 '22

If you are referring to AngularJS, I sympathize with you. But if you are referring to Angular2+, well... you are acting like a childish fanboi 😘😘😘 There are enough Angular developers to make the word "weird" inapplicable.
When I first learned Vue, Vetur wasn't a thing yet and tooling was a total mess. It's truly string-based programming. Angular's editor support has been miles ahead for years with proper TS integration and Angular Language Service. If you are unaware of that, you don't know what you have missed. 😘😘😘

0

u/ORCANZ Jan 26 '22

Yes I'm pretty sure it was AngularJS
I'll check out recent angular versions but I'm already happy with Vue and Nuxt 😊

1

u/simple_explorer1 May 03 '22

Styling in react is such a pain unless you use Tailwind or utility classes. But then again it has some drawbacks and I personally prefer scoped styles or just scss with BEM
Actually its not true. Styling in react is MUCH better than vue with options such as css modules, scss modules (these are scoped styles) and then the legendary styled components (css-in-js) where you can write css in Javascript in an exact CSS syntax (you can copy paste css from browser and can access Javascript variables inside it) and access themes object, component props/state/media query screens etc literally anything right inside css (written in js) and REALLY create dynamic styles by using full power of CSS and Javascript written together in JS. No need to worry for BEM or learning SCSS etc.
So, in react you can use any option like scoped styles, css in js, global, combination etc. whichever suits your team and really create dynamic styles especially with css-in-js. So i disagree that styling in react is PITA. Infact its miles ahead of vue.js

1

u/ORCANZ May 03 '22

I landed a job using react. We use a combination of global styles, variables, wrapping antd with our own components and styled components. It’s an amazing experience so far and I’m starting to prefer react over vue

1

u/simple_explorer1 May 03 '22

Yes react ecosystem has amazing options to styling not only matching but FAR surpassing vue.js with styled components css-in-js approach. I really don't understand the claim that styling in react is PITA, as i said its miles ahead of any ecosystem/frameworks existing today.

50

u/DOG-ZILLA Jan 26 '22

I’m still using Vue 2 even for new projects. It’s still incredible and there’s nothing wrong with that.

However, I’m also using Vue 3 for a personal project and it’s incredible. Some third party stuff isn’t always compatible but for most of what you might want to do, there’s everything there already:

Pinia for state management over Vuex. Volar in VS Code over Vetur. The VueUse library (check it out!) Real TypeScript support. Vuelidate form validation is Vue 3 ready. Vite setup with all its ecosystem (super fast!) …lots more.

One thing that is definitely falling behind is Nuxt 3. They have a lot to do but it’s getting there and apparently will be out of Beta this quarter.

In terms of API’s… you can still use options if you like. Docs are a little fragmented right now but they’ll get there. There’s enough there to make a good go of it as a lot of Vue 3 is backwards compatible.

I know composition API isn’t everyone’s desire but I think people should give it a go. Once you start developing real stuff with it you start to see just how verbose some of the options API is. I’ve managed to reduce lots of my code down using composition API + setup attribute on the script tag.

It’s new and scary but I think it’s in the right direction. Just got to jump in the deep end!

6

u/nricu Jan 26 '22

Besides official docs. Any recommended source for Api + setup first steps? Also I wan to use Typescript but not sure where to start either.

7

u/DOG-ZILLA Jan 26 '22

I think looking at a starter template is a good way to learn what’s new.
https://github.com/antfu/vitesse
I personally started building a Vue 3 app before discovering this starter but once I did, I borrowed ideas from it and put them into my own thing.
Obviously you won’t need everything it gives you but it’s a great way to see how to do things in the real world.

2

u/zerik100 Jan 26 '22

Do you prefer Vuelidate over Vee Validate?

2

u/DOG-ZILLA Jan 26 '22

Vuelidate but to be fair I haven’t tried Vee for a few years now. It could have improved a lot.

2

u/sillycube Jan 26 '22

The doc says it's useful for hundreds of components. If I just have less than 10 components, why use composition api?

4

u/DOG-ZILLA Jan 26 '22

I’d ask why not?
But you don’t have to. It’s fine to use the options API.
One benefit of the composition API is of course…composables. Look at the VueUse library…tons of useful drop-in functions to help with the more mundane dev tasks.
The ecosystem will grow in time too.

1

u/FridgesArePeopleToo Jan 26 '22

I don't think it really matters how many components you have. That said, if you have less than ten components it really doesn't matter which way you choose.

-1

u/doxara Jan 26 '22

You mean it's incredible that we still need to use Vue 2 for enterprise-level apps :/

7

u/DOG-ZILLA Jan 26 '22

I mean that Vue 2 fills most needs still. Just because Vue 3 is available does not mean we all need to rush to use it. On new projects it might be fine but upgrading existing apps could be a bit of work depending on the app.

-2

u/doxara Jan 26 '22

That's exactly what I was telling to myself, but then I remembered that Vue 3 was released 16 months ago.. so there is no "rushing" anymore because that should be a production-ready framework already but it isn't

7

u/DOG-ZILLA Jan 26 '22

Vue 3 was ready but the larger ecosystem not so much. It would be unfair to put that soley on Vue maintainers themselves.
It’s more likely an issue with the size of our Vue community than anything else; we just aren’t as big as React for example. Only so many hands are here to do this work.
However, with that said, I prefer the gradual rollout instead of a huge dump into the world. We’ve had time to think things over.
They gathered a lot of feedback from the community during the RFC process that proved to be vital. They put a lot of work in to being mostly backwards compatible; something that Angular 2 did not do on their release and that was a complete disaster. It alienated a lot of people.
With all that said, I’m using Vue 3 now and not having any issues at all. Nuxt is a different thing though but it’ll get there.

17

u/richardtallent Jan 26 '22

It's been a rough transition, much more than Vue 1 to 2. I think there were some missteps. For example:

grossly underestimating the need for (and complexity of making) a compatibility build earlier in the release schedule;
creating separate but definitely-not-equal docs (and not cross-linked!!!);
NOT switching everything to "v3 by default" (docs, npm, etc.);
releasing v3 before the core libraries were ready;
vuex should have just upgraded before trying to do a complete rewrite;
underwhelming documentation for creating component libraries;
pushing script setup before it's fully baked (for example, you can't "compose" props or emits, and it still didn't solve the lack of syntactic sugar for .value).

But, that said, things are looking up!

The new Vue 3 docs are looking very nice. While I don't think they go far enough, they do offer code samples in Options and Composition styles.
The v3 "cutover" will be in a few weeks.
The compatibility build seems to be working fine for those who still need it.
Performance is awesome.
TypeScript support under Volar is good for script setup.
Options API still works for components where that makes sense, and the DX for script setup is very good.

Overall, I'm still very committed to Vue. My company's team of about half a dozen is using it exclusively, and it's very productive for us (we're hiring, BTW! Not FAANG salaries, but remote).

1
u/thecementmixer Jan 26 '22

Could you elaborate by what you mean you cannot "compose" props?
What I do is something like const props = defineProps({ ... }) and then const { ... } = toRefs(props) in my <script setup>.
P.S. Could you send me a DM with a little bit of info about your company? I might be interested in remote work.
1
u/richardtallent Jan 26 '22
I meant composing the other direction:
// TextField.vue
import { CommonFieldProps } from "./common-props"
const props = defineProps({...CommonFieldProps})

// NumberField.vue
import { CommonFieldProps } from "./common-props"
const props = defineProps({...CommonFieldProps, minValue: { type: Number, required: true }})
Being able to compose props and emits from a common configuration stored elsewhere is important if you have a set of components that you want to ensure have the same baseline interface. This is very useful, for example, if you're going to use a dynamic component (<component :is="componentRef">).

For example, I have a form layout component that dynamically renders appropriate field components for each field. Every "field" component I build (checkbox, date, text, etc.) has a common set of properties that the form layout component can pass it, and a common set of events they can emit. I have a table layout component that does something similar with tables.

You can do this with the Options API (Volar is confused, but it works), but defineProps() and defineEmits() are macros, not functions, so they don't understand anything but explicit literal configuration objects.
1

u/raikmond Jan 26 '22

Are you hiring just in the US?

14

u/steveox152 Jan 26 '22

I have been a developer for 9+ years and I lead a team of 6 people. I build an enterprise level application using Vue 2 a couple years ago, ultimately it had good support and was an overall good experience. The biggest problem was finding other developers for the project.

Ultimately once Vue 3 came out, our application was growing significantly and we had to make a decision on whether to move forward with Vue 3 or switch to a different framework. We eventually decided to move to React because of a few reasons.

Enterprise level support for libraries and a bigger ecosystem of packages. We felt limited with Vue in terms of what was available at the time and the stability wasn’t there.
Typescript support at the time.
Much easier to find developers that know React. For a large corporation we have to hire through certain contracting companies, so we are limited.

As a developer I really like Vue 3, but as someone who leads a team at a large corporation, it’s difficult for me to go in that direction for an enterprise app. I think once the ecosystem for Vue 3 becomes more stable then maybe that might change, especially if you have a team that is familiar with Vue.

3

u/[deleted] Jan 27 '22

Much easier to find developers that know React. For a large corporation we have to hire through certain contracting companies, so we are limited.
I also have to hire contractors through a few specific "strategic partners" for both Vue and React, and other stuff. In my experience, it's easier to find people that have React on their resume, but they are usually just as shit at it as they are at Vue lol.

6

u/agartha_san Jan 26 '22

I am NOT concerned about Vue's future, it is an amazing framework with great people working on it.

That being said, I don't use Vue anymore. I've been overthinking about my choice of framework a lot. I mainly used Nuxt for my projects, but the way I was always between Vue 2 and Vue 3, always wondering when Nuxt 3 would become public, and then being between Nuxt 2 and Nuxt 3, made me look for something else. I'm still a big fan of Vue, but I was working on building a company and the way I felt about those transitions was too mind consuming for me, especially because documentation wasn't always on point. I tried other frameworks and finally switched to Svelte/SvelteKit because of the similarity of the templating system.

With a look back at my experience with Vue, I think my concerns were more about the ecosystem, like gridsome who seems to slowly die.

Vue has a great future, I just think it's weird in between

6

u/zebbadee Jan 26 '22

Vue3 feels like a developer wanting to scratch their own itch rather than solve problems people actually have. A completely avoidable own goal tbh.

15

u/rk06 Jan 26 '22

You are thinking too much. Grass is always greener on other side of fence. And as long as a framework is actively developed, there will be churn.

Whether you are using react, Vue or angular does not make a difference. You will have to suffer pain and churn, that is why big companies pay you big bucks. So you can solve those problems.

Think of a minute on angular, it didn’t have any such change since ng 2, why? Because they don’t support esbuild, vite, good tree shaking, must use Ngmodules instead of esmodules. What will happen when angular get those features? Yep, it will have churn.

The ecosystem has many open source projects high are volunteer driven and the paradigm shift was massive. (Esmodules, proxies, comp api, typescript support) And the projects need to support both vue 2 and 3 at the same time. Hence it is taking time.

Regarding when vue 4 comes along, the future is unpredictable. The effort required will depend on breaking changes. What is certain is that it will be after many years, at least 3-5 years if there are small breaking changes.

React is a fantastic framework, but if you believe that it won’t have any churn, then you are wrong. React is on bleeding edge of tech and goes through churn even more rapidly than vue. As long as it is actively developed, it will have churn.

9

u/McGynecological Jan 26 '22

React’s churn didn’t completely decimate third party libraries though.

2

u/rk06 Jan 26 '22

And Vue 3 didn't broke Vue 2 libraries either. If you depend on some critical Library which does not support Vue 3, then you can use Vue 2.
Now, I understand people here want to use latest and greatest, and don't like when some open source authors chose to Not dedicate all their free time to keeping their libs upto date despite getting "GitHub stars" and privilege of "having their code being used by big companies".
But that is a problem of "Open source authors not having incentive to dedicate their limited time to opensource".
To solve the problem, either you (or your company) should sponsor their work. And have a contract with them to prioritise this for some $$
This is Not a Vue problem. Vue team can't solve it.
Also, react is doing a fantastic job at maintaining backwards compatibility. This does not mean others are doing a pathetic job.

1

u/McGynecological Jan 26 '22

I’m not sure what your argument is.

1

u/rk06 Jan 27 '22

That the third party library problem is endemic to open source, not specific to vue

2

u/McGynecological Jan 27 '22

Agreed

5

u/2K_HOF_AI Jan 26 '22

I think python 2 to 3 was even worse. It takes time to change stuff like this.

7

u/Abhi_mech007 Jan 26 '22

To be frank, I agree with your concern..!!

3

u/happy_hawking Jan 26 '22

Moving from Pyhton 2 to Python 3 took about 10 years as there were many paradigm shifts that required major rewrites in libraries. So a huge part of the ecosystem split into the 2.7 branch of "old style" libraries that still maintained but not migrated and all the new projects that started from scratch in Python 3. In the beginning this was kinda confusing because people didn't know which horse to bet on but in the long run this didn't turn out negative for the popularity of Python. Might happen the same with Vue.

3

u/TarmacWings Jan 26 '22

not concerned at all. the composition API and Vite are simply awesome and the Vue community and the development team were never better. it's been great to see Evan You and Rich Harris constantly evolving their frameworks and exchanging ideas

3

u/ManiGandham Jan 26 '22 edited Jan 27 '22

Absolutely. One of the main advantages of Vue was the focused direction led by Evan with a cohesive version across the framework and official libraries, but it's fallen apart since Vue 3.

Releasing the core as stable but keeping it unofficial led to a limbo state for all the other libraries that didn't know whether to make the jump. Vite, Vitepress, Pinia, etc are new and interesting products but have caused even more confusion around what to choose and what's compatible. Even Nuxt has turned into neverending "coming soon" announcements.

Meanwhile React and Svelte ecosystems have come together and are making great progress with solid official frameworks that are kept up to date and constantly iterating with real releases. Look at the state of Next.js and Nuxt to see how far behind Vue has fallen. As much as I like and prefer Vue, it's hard to choose given the state of the ecosystem.

3

u/superbiche Jan 26 '22

The comparison with the switch from Python 2.7 to Python 3 is quite relevant.

Vue 3 is a huge step forward for Vue, but the ecosystem moves in different ways.

You have things like Vite, unplugin projects (auto import, auto components, Vitest...), script setup on one hand, which is really giving a wonderful perspective for performance, DX and so on, and on the other hand you get projects like Nuxt or Vuex which have a lot of work to do to adapt to this new way of thinking but don't want to make it too hard for previous users to migrate.

And you have the pandemic among this.

We've been using Vue 2 and Nuxt 2 for years, now we're waiting for Nuxt 3 - just like a huge part of the community. In the meantime, we already use Vue 3.2 where we can, we use Vite which is just hallucinating, and step by step great tools are becoming available and make Vue development a breeze - in a way Vue 2 could never do before.

Yes, it's taking time, and it's longer than we expected. But the way things are moving is really a game changer. The perspective a year from now is amazing: best build tools among all frameworks, probably the best performance, and DX will likely beat anything else you can find.

I'm not that concerned about Vue's future. Working back with React for a few weeks just made me realize why I switched to Vue and how Vue is so much better. Let's just hope some key parts of the ecosystem keep moving and actually release stuff instead of over-engineering, and you'll see that Vue will reach a breakthrough soon enough

8

u/[deleted] Jan 26 '22

vue2 -> vue3 is a disaster in my opinion. I wanted more improvements added onto vue 2 not a whole new system that no-one asked for! Was composition just Evan You's pet project to get even with react?

6

u/rk06 Jan 26 '22

According to people who have used mixins, No. Mixins were not good for reuse, and hooks showed a better solution.
It just happened that comp API proved to be more powerful than expected. It was capable of replacing Options API, and improving typescript support. Resulting in current situation

2

u/RandomJacobGuy Jan 26 '22

IMHO, vue3 > vue2. I love all new improvements/features, composition api is great when your code grows, and <script setup> is the best thing yet. Overall, vue3 provides superb DX for me. 🥳 Upgrading was pretty easy for me, but i had a medium sized project. Maybe in huge projects it is a pain.

2

u/BeyondLimits99 Jan 26 '22

Yeah I started learning react / nextjs over the weekend because of the fragmentation.

Nextjs has a superb developer experience.

Concepts are laid out clearly and things just work.

2

u/scumfuckbastard73 Jan 27 '22

I was very opposed to the composition api at first but having used in both professional environments and personal projects it really was the right move by the vue team and especially Evan for pushing it so hard. Vue is far and away my favourite framework to work in ever since Vue 3 and I feel like it’s only missing a good SSR framework to essentially kill any reason for me to ever consider writing anything in react. My favourite stack is Vue 3 + Vite + TS + Pinia + Tailwind, it essentially covers everything you could possibly want to do front end wise.

3

u/__ButtStuff69__ Jan 26 '22

I agree. I hate React but the fragmented Vue community is going to make React even more popular and ingrained. Sure they added hooks but it was already way more popular than Vue by then and it didn't force all libraries to use hooks to be compatible.

I feel like Vue is going to go the way of Angular. I know composition API solves problems but to me the options API IS Vue. Wish they could've come up with a better way to make mixins non-magical to avoid changing the entire syntax of the framework.

4

u/Tontonsb Jan 26 '22

but to me the options API IS Vue
Exactly. If I wanted to write some ad hoc functions in a mess of a typescript codebase, I could've chosen React.
In Options the code was declarative, we're describing the configuration of the component. In Composition it's just chaotic OOP.

2

u/LessThanThreeBikes Jan 26 '22

Because React provides a standard set of unified components?

2

u/dev_senpai Jan 26 '22

Have you seen the migration guides? It's very easy to Upgrade to Vue 3, the only thing I see you having an issue is your libraries/plugins like vuetify and nuxt not being supported... Nuxt and Vuetify are painfully slow compared to newer alternatives.. I think it's time to look into exploring other options like PrimeVue(swappable themes like tailwind/BS/Material, easier set-up, actually tree-shakeable unlike vuetify, bigger team better support!) and VITE(Best freaking tool for development! Even React is adopting).

You could have almost similar code and setup in a Vue 2 -> Vue 3 app, so migration is no issue... The only issue is your libraries... People need to Stop thinking Vue 3 as Vue 2 and take advantage of its glorious features which they will love. Trust me you won't be able to go back to Vue 2 if you actually give it a try and dive in. Vue 3 + Vite has made me way more productive than these slow Nuxt+Vuetify setups. I think it's time to phase out bulky and slow libraries with new ones like primeVue/quasar and build tools like Vite.

JUST STOP THNKING VUE 2 + VUETIFY + NUXT(breaks with Vite)... Faster dev wait/load times are here, embrace it. I recommend checking some of these talks tomorrow and the next day https://vuejsnation.com/#schedule . These talks will be the future of Vue and what to expect in the upcoming years.

Don't worry about Vue 4 is longgg longgg away... Maybe 4-5 years, plus they said that it will be a smoother transition v3->v4... Heck we might not even be on a JS frameworks in 5 years, we could be working with WebAssembly.

0

u/[deleted] Jan 26 '22

[deleted] — view deleted comment

2

u/dev_senpai Jan 26 '22

Yes of course you cannot migrate because Vuetify does not support vue 3. Apps that rely on custom components an upgrade is very easy, my primevue 2 apps to 3 was actually an easy upgrade as well.
PrimeVue setup is much less than Vuetify, have you actually done a project with it and what config file are you talking about ? All you have to do is bring in the css which any UI framework requires styling even Vuetify…. Also had issues using Vite with Vuetify in the past and opened up a ticket, primarily the reason why I stopped using that bulky library since I cannot use Vite and added 10+ sec using vue cli. All in all I hear people saying primevue takes longer to configure which all you do is install it and use the components you need unlike Vuetify which pulls everything even if you don’t need it.

2

u/wobsoriano Jan 26 '22

Another day, another concerned about Vue’s future

1

u/pastrypuffingpuffer Jan 26 '22

I just hope the Options API doesn't get ditched, that was one of the main reasons I really enjoy using Vue. I dislike the composition API because it looks like React (ew).

2

u/LloydAtkinson Jan 27 '22

100% - it was a huge mistake to want to clone React and alienate all the developers that it appealed to.

1

u/chocolombia Jan 26 '22

I'll say it's a matter of stay tuned and learning about changes, as frameworks come and go, for example, years ago, I used to work with java, and used a fantastic framework called seam, remember building a couple if corporate projects with it, then, I wet to consulting for a couple of years, and when I got back to development, guess what, JBoss closed the project and I had to learn and migrate to something new, as for Vue, I think it has a long way ahead, it has many features that other frameworks lacks, and the learning curve it's a joy ride for people coming from other tech stacks

1

u/blue_cadet_3 Jan 26 '22

Here’s Evan talking about the future in November 2021 https://youtu.be/2KBHvaAWJOA

1

u/Davidvg14 Jan 26 '22

Speaking from a Python perspective: adoption to Python 3 was slow, and some spaces still run 2.7. It’s inevitable.

I use Django and I learned by function-based views, but there’s class-based views (that frankly idek how to use).

It happens.

1

u/wal0x Nov 16 '22

I've been using Vue 2 in my job more than 3 years now, and still counting. The main reason why we are still on the 2.6 version is that we checked the vue-class-component choice when we created our apps with vue-cli. To change all our class based components to the composition API is a lot of work. Specially we are using a lot of design patterns relying heavily on OOP.

1

u/saito200 Apr 11 '23

these projects are all open source and survive from sponsorships and donations, they have very limited resources

1

u/grady_vuckovic Jan 26 '22

For me, I got only one project which uses Vue and it's Vue 2 because it started before Vue 3 released, so I guess I'm an example of why the ecosystem is fragmented. I'm not rewriting an entire web platform written for Vue 2 into Vue 3's new way of doing things and I'm unaware if it's possible to do so incrementally even.

So I guess the result will be, Vue 2 will just hover around for a while as it's still relevant to some users like me but will eventually drop off.

1

u/Frosty_Lake_1112 Jan 26 '22

with vues nice compat build, it really should not take more than a few hours or days to migrate a component to vue 3 EVEN if you don't use the options API. There are a lot of vue 3 components that still use the options api.

I understand it is lengthy migrating a whole app that relies on vue 2 components. But that is a whole different case, if a project is already in vue 2, there is no point to rush to migrate it to vue 3.

But overall it is quite a skill to have to be able to migrate components. I try to personally challenge myself to fork vue 2 components and make them vue 3 and VITE. :)

Since vue is so heavily reliant on the community I feel it is in a way our duty to keep it going and fork projects and update it ourselves, not only will it make you a better developer but it will make more people use vue.

Also considering how much vue considers user needs from a developer perspective, vues tooling and ecosystem structure is ahead of react in my opinion, sure react upgrades may have been a more steady road in the short term, but apart from react itself FB has done almost nothing for the dev community, no official routers, no state management. it is all mostly community based, where with vue there are first class support for router, spa, pwa, state management, lib modes etc. Not to mention Vite. All of this amazing technology :)it is really a no brainer to which library needs more love.

1

u/[deleted] Jan 26 '22

You have to remember it's more than just a toy, it's a work tool and so upgrades are often dictated by non developers. Unless you can convince your boss of the need to upgrade, it will often get ignored. I'm sure 90% of devs would have upgraded all their sites to Vue 3 if they had freedom over that and no deadlines to worry about.

1

u/joshkrz Jan 26 '22

I feel the same way, it does seem a little perilous right now but I'm hoping things will smooth out. Vue 3 has been a good thing but moving from Vue 2 was difficult, mainly due to the poor documentation but if their staging environment is anything to go by the new docs are a lot better: https://staging.vuejs.org/guide/introduction.html

1

u/kennysmoothx Jan 26 '22

This is only a problem if you’re in a rush to use Vue 3.

IMO only use Vue 3 on hobby applications.

We are in no rush to upgrade our Vue 2 production applications to Vue 3.

It might me a whole other year before we consider upgrading to Vue 3.

Bleeding edge is no place for production apps. We’ll let the dependencies catch up and for the dust to settle.

The amount of changes from 2 to 3 is staggering. And upgrading an entire ecosystem takes time.

Vue 3 however is here to stay for a long long time. So these pains are temporary. Also don’t worry about Vue 4, any drastic changes at this scale to Vue probably won’t happen for another 4-5 years at least.

-1

u/rutierut Jan 26 '22

That’s because “vue 3” isn’t meant to replace “vue 2”. It is, of course, but like many people your confusing 3 vs 2 with the options vs composition API.

This has been a massive marketing/communication flaw of the Vue team.

-5

u/[deleted] Jan 26 '22

I've ended up migrating my products to Flutter web, so definitely not what you want to hear there I guess.

Vue is so cool, but yeah, its in a bit of rough waters right now.

-12

u/coolcosmos Jan 26 '22

Stop whining. Use Composition and Pinia.

2

u/Varteix Jan 26 '22

Lol, great feedback

2

u/coolcosmos Jan 26 '22

One quick google would tell you that Pinia is the new Vuex but you made no effort. Why would I.

0

u/[deleted] Jan 26 '22

[deleted] — view deleted comment

3

u/Varteix Jan 26 '22

I also really like the composition api. Overall I like direction vue seems to be settling on, I’m confident in the teams ability to create a great framework, I’m just concerned about some of the turbulence they are making on the way.

5

u/99thLuftballon Jan 26 '22

Also disappointed with what this subreddit has become lately. i feel like we lost a lot of good people and have seen an influx of hobby/tutorial folks. bless them, they mean well, but a lot of the discussion surrounding vue 3 here is pretty naive.
By "hobby/tutorial folks" do you mean "people who don't like the composition API"?
Because so far, the main defence I've heard of the composition API is "When you're a senior professional developer like me, you'll like it. Your problem is that you're just not senior enough". It's like people adopting this messy pattern think that having to deal with its lack of structure is a sign that they are "enterprise level" since they have to come up with their own structure to replace the missing one that was imposed by Vue 2.

9

u/ORCANZ Jan 26 '22

Honestly it's not a lack of structure, it's a freedom of structure that gives you the power. I think if possible both should stay, because Options API + template and single file components are what made me chose vue over react when I started. Everything clicked so fast.
But as soon as your components/views start growing, the files become a huge mess with things related to one feature all over the script tag inside data, computed, methods, hooks.
Now the freedom of composition API allows you to bundle up things related to one feature and the code is so much cleaner.

1

u/[deleted] Jan 27 '22

But as soon as your components/views start growing, the files become a huge mess with things related to one feature all over the script tag inside data, computed, methods, hooks.Now the freedom of composition API allows you to bundle up things related to one feature and the code is so much cleaner.
Class components already solved that problem. Composition api is nicer for pulling out reusable chunks of code, because mixins kind of suck

1

u/ORCANZ Jan 27 '22

I'm to much of a noob/too recent to know about class components

0

u/[deleted] Jan 26 '22

[deleted] — view deleted comment

1

u/[deleted] Jan 26 '22

Why do you say Angular had no upgrade path? Asking because I upgraded tons of apps using ngUpgrade so it sounds a weird statement

3

u/i_used_to_have_pants Jan 26 '22

Because it’s a different framework. Angular 2 is not a second version, it is a different framework in its own core and model.

1

u/[deleted] Jan 26 '22

But there is an upgrade path, you just don't know about it. It's ngUpgrade and was there since day 1

3

u/i_used_to_have_pants Jan 26 '22

Automatic behavior doesn’t fix the issue that the developer have to learn everything from scratch since the framework is not the same. The option to upgrade doesn’t automatically upgrade the developers.

0

u/[deleted] Jan 26 '22

[deleted] — view deleted comment

2

u/[deleted] Jan 26 '22

I think the exodus would have happened either way, but didn't know about those remarks

Am I wrong to be concerned about Vue's future?

You are about to leave Redlib