Many “reactive” state libraries try to fix performance with atomic state splits, but that often fragments logic and hurts scalability.

What if instead of atomizing state, we atomized subscriptions — so updates stay precise, but the model remains holistic?

That’s the line of thinking I’ve been exploring lately with a new approach to reactive state management.

Has anyone else experimented with that idea?