Thanks for the feedback, @cmc333333 and @ascott1.

Yeah, so, Dispatch seemed nice in theory, but in practice was very hard to understand and the related event context was anyone's guess. Additionally, the new solution means that there's context to each event. Example, 'section:open' can mean something different to the main content view vs. the sidebar. Before, that was technically the case, but we had all areas responding to a single event that would trigger an async action, and things could get messy. Now, the area that has significant async activity - the main content - can tell other areas about a 'section:open' at the appropriate time. The band-aid solution was to create extra events like "section:open:after" but that doesn't actually *mean* anything. I *think* things read more consistently now.

I gave the tighter coupling downside some consideration, but I am *hoping* that the division of views and their associated buses are a net gain on cognitive overhead. It can get a little verbose, especially around declaration of module dependencies, but I think it makes it a teeny more transparent.