Wait... what happened? Did Vue make itself all shitty when I wasn't paying attention?

Anyone loving version 3?

I like the Angular 1.5ness of Vue 2. If it's going to try and be more* - then we already have Ember.js

I haven't actually used vue 3 in it's full potential, but I like the idea of the composition API, not sure if it's any good in practice though.

I heard awhile ago that the Vue people say themselves that migration from 2 to 3 is awful. That's why they encourage for version 2 projects to keep doing their thing.

I feel the composition API was just installed to lure away react people by adopting an inferior declarative strategy, and in the process gives up it's competitive advantage to gain a little marketshare. And as lasagne mentions, it accomplished it by inducing broad scope breaking changes on its existing users, which is poor form.

Composition API looks nice, it is amazing and beautiful and then it turns into hell...

ember.js? So many js’s to learn, so little time. It’s like all the js’s are ganging up and beating on me lol. When I learn one js another one comes out. When I learn the new one, I forget the js I learned prior...or it gets new updates that I miss out on and that I “must” learn

@d-fanelli
Same, never heard of ember.js until now... I though Vue was all the rage these days, just started learning it earlier this year for fun...

@d-fanelli I think you caught yourself in tutorial hell where they wrongly use words "must" and "necessary".

New docs of Vue are awful to tackle. They don't evolve in something better, and that will remain a problem. Composition API isn't even getting enough spotlight as it should. I really liked that approach, and it just sits there in god forgotten "Advanced" section of Vue docs. It's not that "advanced" to explain on fingers, ffs!

By the way, I keep hearing good stuff about latest Angular, so I'll try it on my next project.

@lamka02sk care to explain? For me it actually solved quite a few problems that with vue2 just felt "wrong". The only thing im really missing in vue (dunno if other frameworks have it) is being able to watch a giant object (for example an array) and see WHAT has changed in the watcher. Not talking about a diff, just sth like "elements 1,2,3 changed"

However, as with OOP i think overdoing it can be a problem, so i don't use composition api for small components where it for me doesn't add anything.

@d-fanelli it’s likely - that you should just learn JavaScript then. Once you need something like Ember, you’ll know. Depends on the project size.

Just at a basic level: I make little Vue prototypes all the time in CodePen. I figured I should use the newest one / but couldn’t get anything to work. No backwards compatibility? Not even a little - and a warning?

@eval I actually prefer composition api with small components. At least over options api. Can’t say about large ones, since when a component gets too large I break it up into several components or refactor it as composables.

That being said, I think there’s lot to like in Vue 3 and the composition api - however the tools around it in the Vue ecosystem (apart from Vuex), ie vue-i18n etc are not quite ready yet for migrating from vue2 > vue3, so for any prod workloads I’d wait a while. One difference that really bugs me is how they changed to reactivity system into a more explicit and less dev-friendly one.

For maintainability, Vue 3 takes the throphy hands down. It is possible to write clearer code with a better structure within vue files than it was before. All in all, it takes some time to get used to it, and migration from vue 2 > vue 3 is a hell, since there are so many breaking chances and if you want to take full advantage of the composition api you’ll have to rewrite most of your scripts.

@100110111 there should be a way to incrementally move over. At least in dev - have both systems run side by side.

@sheriffderek there is though?! Vue3 is backwards compatible if enabled...

@eval ah. That’s cool. Well, they should put an error in the console when you create a new Vue instance 2.0 style with 3.0 instead of shitting the bed.