Decide which state management tool to use

[GeniaT]

Hey there,

A state management tool is still to be defined and added to the tech-stack.
Continuing the discussion from Discord, a few options we have: Redux , MobX , use of ContextAPI, ... Please share your view and list any other interesting option that may exist.

I personally didn't work with MobX and use ContextAPI as a substitute to Redux doesn't seem a right choice to me. So it would be Redux for me.

What tool would you go for and why?

[robertt]

While I ❤️ mobx, it would definitely not be good for beginners (decorators, RxJs, etc). Context is nice for small apps but I don't think it would be good for big sites like this. I'm all for Redux, maybe with thunk.

[Zeko369]

I agree with both of you, Redux with thunk ❤️

[ThomasRoest]

I would say the opposite, Mobx is easier to understand. Less boilerplate and less files to navigate through.

[h7y]

Since redux is widely used and there are tons of free resources available online to get familiar with it, It'll be welcoming for both new and existing contributors!

[eolculnamo2]

I know there was push back in the chat, but I'm voting React Hooks (useContext with useReducer). :P

If we go Redux, I'd personally prefer Sagas.

I'm on board with whatever the decision is though.

[nik-john]

useContext isn't really a mature feature with widespread adoption yet and like @Haxified has mentioned, it isn't particularly well suited for complex apps. I would go with the tried and tested libs like Redux. @timmyichen I am yet to work on a Production app on Next + Redux, though I know it is a widely used combo - would you have experience on this?

[timmyichen]

We used Next + Redux at Repl.it and it worked fine. They don't really have much intersection so it's really the same as any other React + Redux app. I'm also fine with Redux being used as there are lots of resources available for newcomers to learn from.

[nik-john]

Cool that sounds good @timmyichen - I was just wondering about the server-side hydration on first load and re-hydration on client render and if there might be pitfalls that might not be immediately apparent. If it's tried and tested, I'm all for it 👍 👍

[timmyichen]

We did have some wonkiness around that, but only for the more complex parts of our app - I think since we'll be using it for fairly straightforward purposes we shouldn't run into any hydration issues.

[GeniaT]

Thanks for all those feedbacks guys, can we consider this as a consensus for Redux?

[robertt]

Redux 100%, have we decided on using thunk/sagas?

[Zeko369]

Thunk for it's simplicity compared to sagas

[nik-john]

Sagas for easy testability, simplicity 💃 and separation of concerns

[vaibhavsingh97]

Redux with Thunk 💯