Alex RussellJun 3, 2024

My hottest take might be that "state management" isn't a real class of either problem or solutions. Instead, it seems to cover a confusion of:

- intra-component data propagation
- a bad way to reinvent events and broadcast channels
- a missing data synchronization layer

Each of these have distinct solutions, and "state management" tools do none of them credibly.

Show threadMunawwar FirozJun 4, 2024
@slightlyoff At the heart of the good "state management" libraries, it's just this. But it's being built by random people over and ocer again because certain framework authors are focused on "the next big thing" (narrator: which isn't) than clearly addressing something that is missing in their "framework" and is causing confusion.
Show threadmatthew
imo, it's built over and over because view and state are separate asymmetrical hierarchies and the view is the focus of component-oriented architecture.

CC: @[email protected]
Jun 4, 2024 at 3:33pmWeb
Show threadMunawwar FirozJun 4, 2024

@matthew As I see it, It's still all about view. And a FW without some tools there feels incomplete.

The built-in solution doesn't need to have loads of bells and whistles. For more advanced solution use a 3rd party solution if needed. One can see a pattern in the use cases majority of these state mgmt libraries are addressing.