Vue.js

446 readers

10 users here now

founded 1 year ago

MODERATORS

Ategon@programming.dev

why Vue over React? (programming.dev)

submitted 1 year ago by 0110101001100010@programming.dev to c/vuejs@programming.dev

6 comments fedilink hide all child comments

We have a Vue frontend and I'm getting some feedback when we upgrade to Vue3 we should move to React just for the ecosystem and dev availability. I thought Vue was a better/faster/easier response to react. What are your thoughts?

you are viewing a single comment's thread
view the rest of the comments

[–] codepoet@programming.dev 0 points 1 year ago (1 children)

Truth. As someone who cares more about getting the job done and done well, Vue 3 seemed like a step back to me. If it's moving to be more and more like React, why wouldn't I just use React? These frameworks don't need to be as complex as they're being made to be, and Vue 2 proved that. Vue 3 loses the magic for me.

[–] xoggy@programming.dev 3 points 1 year ago

I will say it took a bit of warming up to the composition API but referencing the static variables as opposed to this.variableName made it easy to spot a bunch of dead code in our components. I also don't have to think about reactivity like I used to. Vue.set and Vue.observable just aren't necessary any more. So from a surface level it seems you're more abstracted and removed from the target browser code it outputs but from a cognitive overhead standpoint it's been a simpler, cleaner experience using the composition api and build toolchain.

My only complaint is inside the script block you have to reference computed values as variableName.value instead of just variableName. If it wasn't for eslint to tell me I forgot to type ".value" when referencing a computed value in the script block I'd probably screw this up a lot. Having to depend on eslint to address a shortcoming in the api feels wrong to me.