Redux or Context in React 

Hi.....Even I have used Easy Peasy and really loved it...Thanks man

Thanks @Sean Matheson, we can use a tool to debug "easy-peasy" like redux Dev tools ?

@@engenglish610 You can use the redux Dev tool itself, cz easy-peasy is just an abstraction layer over redux and thunks

yeah you can setup things where the rerender isn't a big deal for context, but in some scenarios is simpler to use a state management lib

Thanks @Joseph. Hey Ben, can you make a video how to do this?

@@bawad What font are you using in this video? I want it!!!

Hi guys. Can you please give your opinions on whether to use redux or context for a cart? App is a order management system where users place orders for multiple products. ( Retailers ordering from distributors )

The problem is when you have other states inside children of a context provider, every time the context state changes, everything inside the provider gets re-rendered and the internal states go back to their default value. Let's say you have a state that manages if a kebab menu should be open and the state is set to true as default, every time you update the state provided, assuming this menu state is inside a component that is a child of the provider, it will always be set to true, so, every action you make that changes the provided state will open the menu because it will re-render the entire component tree and set everything to their default values. That applies if you make a [count, setCount] state inside a provider, whenever you update the provided state, the count state will reset.

I know im 1 year late but they already offered a solution, check the useContext docs

Did you try SSR with ReactN?

@@IvanKleshnin no Ivan, just on some mobile projects

Yeah

Younes Your question cleared my doubts as I use reselect in a fundamental part of my RN app, thank you so much!

it can be depending on the situation

both are bad you should be calling setState

useReducers can only be used in it's own component or pass down as props therefore it cannot be consume as context in any child component. PS - pls correct me if I miss something

@@tkdevlop Technically you can pass usereducer reducer as context with both state and all actions you can perform, but i'm not sure how it would click in the end

useReducer is great for local state for state across multiple components, you can combine it with context but you'll run into the same problem

It won't beat React because of the ecosystem. It's too late in 2019 to enter the framework battle. I personally wouldn't waste time to learn another "promising" framework. There are better topics to spend your time on.

I tried the getting started and it was pretty cool, but I'm not ready to switch from react

@@bawad I am in the same situation. I like the React (everything JS) concept. I don't want to learn a new templating standard. I wish React introduces some kind of precompilation to avoid larger size bundle etc. But we have to realize that there is no Status Quo in our world. A new better one will always replace an old less good one.

@@bawad Check this out ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-AdNJ3fydeao.html

@@IvanKleshnin Check this out ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-AdNJ3fydeao.html

easy-peasy is Redux with an abstraction layer...