Alex Russell on Nostr: My hottest take might be that "state management" isn't a real class of either problem ...
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.
Published at
2024-06-03 16:43:16Event JSON
{
"id": "d57b90a551e962857388b1af4f0caaf76e1e4e2321bc112f6a69ddceb45eebfe",
"pubkey": "0a6a259cdd6b1549c96091aa012f0552bdc4a36f2585efffe059eeb235391ddc",
"created_at": 1717432996,
"kind": 1,
"tags": [
[
"proxy",
"https://toot.cafe/@slightlyoff/112553688855732438",
"web"
],
[
"proxy",
"https://toot.cafe/users/slightlyoff/statuses/112553688855732438",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://toot.cafe/users/slightlyoff/statuses/112553688855732438",
"pink.momostr"
]
],
"content": "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:\n\n - intra-component data propagation \n - a bad way to reinvent events and broadcast channels\n - a missing data synchronization layer\n\nEach of these have distinct solutions, and \"state management\" tools do none of them credibly.",
"sig": "9780d84dc95f86c722dc6dd0193d57cb35b2798cb4857841b3e8ad52271c5797e0725e7fc0b00025ba759e5155a8baa301b744ff87c0ceae84803fa8bdc837f0"
}
