3 ms·

I've been doing some research recently and it continues to be by far the most popular state management framework for React. The fact that there are alternatives

I've been doing some research recently and it continues to be by far the most popular state management framework for React. The fact that there are alternatives doesn't mean that most projects have abandoned it.

soft_dev_person 4y ago
Do these metrics count "no framework" as an option? With hooks, context and separation of concerns, most apps can live very well without any "state management framework" at all.
meindnoch 4y ago
Has it occurred to you that maybe “state management” is not something you need a framework for?
- Jasp3r 4y ago
  Tell me you're not making complex webapps without telling you're not making complex webapps
  - idlewan 4y ago
    The publish-subscribe/observer/mediator pattern is perfectly fine for state management, and doesn't need a framework. At most, a small-ish library, but you can also re-implement it yourself quite easily. Reading your comment, I have the impression you took it as "there shouldn't be any state management necessary", instead of "state management doesn't need a framework" sense.
    - ketzo 4y ago
      "State management is complex, so we used a framework to make things easier." "Why use a widely popular, well-documented, battle-tested framework? Just have one of your senior devs build something over the weekend. This will definitely reduce complexity." Like... I get what you're saying. But "build your own" is not a default answer for an extremely complicated software engineering topic (which, yes, state management is!)
    - acemarke 4y ago
      FWIW, Redux literally _is_ a pub-sub/observer pattern implementation :) And the Redux core library _is_ extremely small. But, that led to the community building hundreds of addon libraries for the same sets of use cases, which is what led us to build our official Redux Toolkit package to simplify standard Redux usage patterns.
- ThePadawan 4y ago
  This relates in no way to any statement from the comment you replied to. Did you mean to reply to a different comment?
  - ASalazarMX 4y ago
    > [..] the most popular state management framework for React [..] Quoted from the comment they're replying to. > [..] maybe “state management” is not something you need a framework for? Quoted from their reply.
    - ThePadawan 4y ago
      Ah I beg your pardon. I read the comment in completely the wrong tone of voice. To me it seemed like the comment was attacking its parent for investigating state management frameworks in the first place - when it in fact called out "no framework" as a valid alternative to any number of frameworks. (I hope that made sense)
      - meindnoch 4y ago
        Exactly.

soft_dev_person 4y ago

Do these metrics count "no framework" as an option? With hooks, context and separation of concerns, most apps can live very well without any "state management framework" at all.

meindnoch 4y ago

Has it occurred to you that maybe “state management” is not something you need a framework for?

Jasp3r 4y ago
Tell me you're not making complex webapps without telling you're not making complex webapps
- idlewan 4y ago
  The publish-subscribe/observer/mediator pattern is perfectly fine for state management, and doesn't need a framework. At most, a small-ish library, but you can also re-implement it yourself quite easily. Reading your comment, I have the impression you took it as "there shouldn't be any state management necessary", instead of "state management doesn't need a framework" sense.
  - ketzo 4y ago
    "State management is complex, so we used a framework to make things easier." "Why use a widely popular, well-documented, battle-tested framework? Just have one of your senior devs build something over the weekend. This will definitely reduce complexity." Like... I get what you're saying. But "build your own" is not a default answer for an extremely complicated software engineering topic (which, yes, state management is!)
  - acemarke 4y ago
    FWIW, Redux literally _is_ a pub-sub/observer pattern implementation :) And the Redux core library _is_ extremely small. But, that led to the community building hundreds of addon libraries for the same sets of use cases, which is what led us to build our official Redux Toolkit package to simplify standard Redux usage patterns.
ThePadawan 4y ago
This relates in no way to any statement from the comment you replied to. Did you mean to reply to a different comment?
- ASalazarMX 4y ago
  > [..] the most popular state management framework for React [..] Quoted from the comment they're replying to. > [..] maybe “state management” is not something you need a framework for? Quoted from their reply.
  - ThePadawan 4y ago
    Ah I beg your pardon. I read the comment in completely the wrong tone of voice. To me it seemed like the comment was attacking its parent for investigating state management frameworks in the first place - when it in fact called out "no framework" as a valid alternative to any number of frameworks. (I hope that made sense)
    - meindnoch 4y ago
      Exactly.