4

React Context + useReducer - Still to this day my favorite way of managing global state in React, no extra dependencies, no learning curve, it's all there built-in

top 3 comments
sorted by: hot top controversial new old
[-] ElkanNixed@programming.dev 1 points 2 years ago

It really depends on what kind of state you're storing. For UI or other client stuff usually a context provider is enough. For server data/state I started using React Query a lot more. It syncs server data across components that use the same cache key, which is really powerful.

[-] RadiantDew@programming.dev 0 points 2 years ago

Just curious - have you applied this in big React applications?

The reason I'm asking is because all context consumers get re-rendered immediately upon context value update. It might be ok for small apps but bigger apps can suffer.

[-] cufta22@programming.dev 0 points 2 years ago

Small to medium this can definitely work, large scale ( ex. Airbnb ) still works better with redux but i still see people misusing redux in smaller apps where you don't really need it

It's not just redux people really like to overengineer stuff nowadays

this post was submitted on 26 Jun 2023
4 points (100.0% liked)

React

1104 readers
1 users here now

A community for discussing anything related to the React UI framework and it's ecosystem.

https://react.dev/

Wormhole

!pico8@programming.dev

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS