Good points. A response:<p>1. Global state is easier to see on a high level, but harder to reason about. Local state is inherently easier to reason about: it&#x27;s right there. Global state requires me now looking at actions&#x2F;signals, global state structure, and then my component, and resolving the three.<p>2. They should definitely be synchronized, this problem is only specific to local state implementations today. If they aren&#x27;t synchronized, thats simply at the lack of the system you&#x27;re using. I&#x27;m not familiar with Om Next, but I&#x27;d guess it handles this for you (as could any system properly organized).<p>3. Not true. You could have state changing functions imported and used by multiple components. This is also easier to understand, in my opinion. I can see where the state is located, and still keep my shared state changing functions somewhere.<p>I do think local state is skewed negatively now because it&#x27;s very poorly done. React, angular, all systems today make local state a total pain, opaque, and hard to work with. Om Next seems to be a step forward (I&#x27;m working on something somewhat related for JS that should make it better as well).