Subscription notification order question

This is maybe a naive question. But I was looking at the Subscription code and specifically thinking about this comment https://github.com/reactjs/react-redux/blob/master/src/utils/Subscription.js#L1-L3

If the goal is to ensure that children are notified after parents, could that be accomplished by an event emitter that notifies in the opposite direction? Like, if the event emitter added listeners to the beginning of the list rather than pushing them on the end? And if that was true would it eliminate the complexity of the nested subscriptions?

[skiano]

@markerikson sure, I am just saying that the hardest part of state mgmt to wrap my mind around in react is what it means to actually connect the components to updates, especially when those components are nested, or worse, if the components care about some of the same events but not the others.

So in a way, I use redux less because of redux architecture itself, and more because react-redux provides a way to connect to redux. In other words, I find myself adopting redux structures (reducers, actions, middleware) not because I want to express my application state that way, but because if I do, I can take advantage of this connector, knowing that it already takes care of things like @jimbolla points out above.

[markerikson]

@skiano : not quite sure I follow what you’re saying there. Can you clarify?