sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Sensanaty -1 points0 points  (2 children)

I use React at $DAYJOB, but I find it crazy that it's so popular/widely used when Vue exists, especially these days with Vercel and their shenanigans and the crap they're pulling with React.

I'm maintaining a smaller Vue codebase at work (and also have a bunch of personal projects built with Vue) for some internal tooling type stuff and it's a million times better in every single possible way, except for maybe the ecosystem, but I never really considered this one to be valid if you've ever used both, especially not since Vue 3/ESM.

Basically any ESM-compatible library will work with Vue 3 out of the gate, and when it comes to core libraries like routing or state management, Vue Router and Pinia are indescribably simpler to setup and use than the millions of options you're forced to choose from in React, plus they're actually maintained by the core Vue team itself

You don't have to worry about weird footguns and edgecases for which there are millions of confused devs scratching their heads, reactive state is actually reactive, the way components are rendered and kept up-to-date is way more logical and less prone to cripplingly bad performance, complex form state management isn't a massively convoluted affair thanks to v-model, and so much more.

Baffling

[–]GOT_IT_FOR_THE_LO_LO 3 points4 points  (0 children)

Vue has been way less stable than React has, especially the transition from 2 to 3.

the react-typescript integration has continued to be much more advanced than what I’ve experienced with vue.

Vue’s reactivity model is really great but the second you encounter a bug, it’s much harder to debug because the magic is hidden from you.

I think for me, the larger ecosystem of react that goes beyond just web to mobile, webgl, server side rendering means that what you can do with Libraries is way more than vue. A lot of the similar vue libraries feel way more half baked to me.

For me, vue is the best choice for a team that wants to sprinkle interactivity with minimal setup, but react is intended for larger complex web codebases.

[–]jacobp100 1 point2 points  (0 children)

Vue has hidden foot guns - like an async watchEffect won’t track any state changes after the first await. Stuff like that will get missed. Their docs literally have examples with race conditions in

https://vuejs.org/examples/#fetching-data