The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showi

The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data because it got mounted too late or something somewhere up the hierarchy changed a key and the component got recreated and its state got lost. I guess as long as long as the component hierarchy fits in your head, it is likely straightforward to reason about all the event interactions. The lifted state model ala redux (and similar alternatives) doesn't suffer from this problem. I personally prefer effector [1] these days because it combines the convenience of event emitter with multiple stores and you usually find yourself thinking much less about what changed the store causing my component to rerender much less often. [1] https://effector.dev/ https://effector.dev/