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.
Alex Russell /
npub1n2…ewrvm
2024-06-03 18:43:16
Author Public Key
npub1n2v4392d52qdnwfdfz4yul9sfqw5uuw9g62v45wsjr82yul44yvsuewrvmPublished at
2024-06-03 18:43:16Event JSON
{
"id": "754375bc3e2de8c594f38bf7ba7d29c6a7896fc4f99fbc567613999a99bd1ada",
"pubkey": "9a9958954da280d9b92d48aa4e7cb0481d4e71c54694cad1d090cea273f5a919",
"created_at": 1717432996,
"kind": 1,
"tags": [
[
"proxy",
"https://toot.cafe/users/slightlyoff/statuses/112553688855732438",
"activitypub"
]
],
"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": "546d633c7e014862fab53d2f7a7c4469dc60ee6996c67c46f297fc9ceb9fe5e74138247d547955ad2c6f1911d8b3548477b0ac97f8f2c5b451734e3d6c660968"
}