4 ms·

Vue 3 perhaps is ready but not its ecosystem. Important libraries (like form management) port to v3 is still in alpha. It was one of the most painful developmen

Vue 3 perhaps is ready but not its ecosystem. Important libraries (like form management) port to v3 is still in alpha. It was one of the most painful development experiences because of that.

The_rationalist 5y ago
newsbinator 5y ago
I can't use Vue 3 in production until Vuetify is close to ready (which it's currently not).
- Hawxy 5y ago
  Same. Vuetify v3 sadly got delayed yet again to Feb Beta/May GA.
- tmm84 5y ago
  This was one of the things I was wondering about. Vuetify is one of the bigger libs for Vue2 so if I were to do some upgrades it would need to be ready.
  - newsbinator 5y ago
    I tried Vuetify with Vue 3 about a month ago in case it was "semi-ready" and lots of basic functionality was still missing. As much as I love working in Vue, Vuetify is the entire reason I use Vue today: if there were a Vuetify for Svelte I'd be using that instead. All the Svelte component libraries, and indeed all component libraries I've ever tried, pale in comparison to Vuetify. With perhaps the exception of Quasar. Using Tailwind after Vuetify feels like going from writing C# to assembly.
yeskia 5y ago
It's crazy how much of the ecosystem is behind, despite Vue 3 technically being available for a while now. Honestly think I'll be looking to migrate away from Vue instead of up to 3.x.
moritonal 5y ago
Yeah, in my opinion they shouldn't have called Vue 3, Vue. If its such a breaking change that most your ecosystem isn't compatible then it should have become its own project and tried to gain adoption by being better rather than brand value.
phil294 5y ago
Unfortunately, not even VueX, the official store management library of Vue, is compatible. There is a huge performance bug [1] that makes migrating larger Vue2 codebases impossible. Pretty disappointing, but noone seems to care. [1] https://github.com/vuejs/vuex/issues/2102 https://github.com/vuejs/vuex/issues/2102
- conradfr 5y ago
  Yeah the synced "official ecosystem" was one of Vue's advantages over React but the Vue3 transition has weakened that. First vue-router and vuex were not ready when vue3 was released. Now Evan You says in this very submission that Pinia is the new store library? I thought that it was destined to be vuex v5 or vuex v5's starting point, after the not-so-great v4. Very confusing. (I didn't even know about Pinia until last week actually, when looking about progress on vuex getters caching). I'm not even sold on the Composition API. It makes sense when I read the doc but basically never when I'm in my actual projects.
Apofis 5y ago
Ooh, you guys also get upgrade anxiety like me. Slow your roll, the latest and greatest will get there. You can always contribute otherwise.
cryptos 5y ago
I consider that an advantage of Angular. You allways get a complete package with everythin updated and consistent.

Vue 3 perhaps is ready but not its ecosystem. Important libraries (like form management) port to v3 is still in alpha. It was one of the most painful development experiences because of that.

The_rationalist 5y ago

newsbinator 5y ago

I can't use Vue 3 in production until Vuetify is close to ready (which it's currently not).

Hawxy 5y ago
Same. Vuetify v3 sadly got delayed yet again to Feb Beta/May GA.
tmm84 5y ago
This was one of the things I was wondering about. Vuetify is one of the bigger libs for Vue2 so if I were to do some upgrades it would need to be ready.
- newsbinator 5y ago
  I tried Vuetify with Vue 3 about a month ago in case it was "semi-ready" and lots of basic functionality was still missing. As much as I love working in Vue, Vuetify is the entire reason I use Vue today: if there were a Vuetify for Svelte I'd be using that instead. All the Svelte component libraries, and indeed all component libraries I've ever tried, pale in comparison to Vuetify. With perhaps the exception of Quasar. Using Tailwind after Vuetify feels like going from writing C# to assembly.

yeskia 5y ago

It's crazy how much of the ecosystem is behind, despite Vue 3 technically being available for a while now. Honestly think I'll be looking to migrate away from Vue instead of up to 3.x.

moritonal 5y ago

Yeah, in my opinion they shouldn't have called Vue 3, Vue. If its such a breaking change that most your ecosystem isn't compatible then it should have become its own project and tried to gain adoption by being better rather than brand value.

phil294 5y ago

Unfortunately, not even VueX, the official store management library of Vue, is compatible. There is a huge performance bug [1] that makes migrating larger Vue2 codebases impossible. Pretty disappointing, but noone seems to care. [1] https://github.com/vuejs/vuex/issues/2102 https://github.com/vuejs/vuex/issues/2102

conradfr 5y ago
Yeah the synced "official ecosystem" was one of Vue's advantages over React but the Vue3 transition has weakened that. First vue-router and vuex were not ready when vue3 was released. Now Evan You says in this very submission that Pinia is the new store library? I thought that it was destined to be vuex v5 or vuex v5's starting point, after the not-so-great v4. Very confusing. (I didn't even know about Pinia until last week actually, when looking about progress on vuex getters caching). I'm not even sold on the Composition API. It makes sense when I read the doc but basically never when I'm in my actual projects.

Apofis 5y ago

Ooh, you guys also get upgrade anxiety like me. Slow your roll, the latest and greatest will get there. You can always contribute otherwise.

cryptos 5y ago

I consider that an advantage of Angular. You allways get a complete package with everythin updated and consistent.