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

  • RadiantDew@programming.dev
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    1 year 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.devOPM
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      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

  • Elkan Nixed@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    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.