Skip to content
loading...

re: The biggest mistake library and framework maintainers make VIEW POST

FULL DISCUSSION
 

Totally agree. At the moment I work on two applications - one is React and one is Vue. The amount of code and complexity on React side to fetch & store data in redux stores is just insane compared to Vue, even though the end result is the same (I use Vuex on Vue side).

It seems like Vue got everything right from the start - Vuex actions are asynchronous so no need for complexity that Redux sagas bring. Vue projects stay lean and easy to expand and maintain.

 

But Vuex is the official solution for state management in Vue right? Redux is an external library, compatible not only with React, and is not even officially enforced. Also there are a lot of data fetchings libs for Redux since data fetching is also not part of the core of Redux, you could just fetch(url).then(res => res.json()).then(data => dispatch(action(data))) and that's all you really need.

 

No one enforce you to use Vuex, if you like you can use Redux even MobX. There are also Rx binding provide from the core team to use those fancy operators. I will say they choose different philosophy. Although Redux is claim to be framework agnostic, but does really people use Redux in Angular... uhm. I'm a both end user, depending on who I'm working with, I can switch Vue and React back and forth.

NGRX is redux inspired library for angular state management. So people kinda use it. Not directly though

Vuex is also inspired by Redux and Flux too.

 

Why are you using Redux? That's your problem...

 

Replacing Redux with Mobx simplified and sped up our codebase. I still haven't found a good way to integrate Mobx with hooks yet though.

code of conduct - report abuse