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

React

868 readers
1 users here now

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

https://react.dev/

Wormhole

[email protected]

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

founded 1 year ago
MODERATORS
 

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
[–] [email protected] 1 points 1 year 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.

[–] [email protected] 0 points 1 year ago (1 children)

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.

[–] [email protected] -1 points 1 year 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