I Really like the third diagram in the Nested Dialogues section and where it says "The wiring of Observables between layers of Dialogues is a data flow graph". This reveals that interactive event flow is primary and is what drives a UI, weaving through components like the nervous system does in the human anatomy.

In the diagram we are looking at an emerging and clear way of defining app flows and structures. There is potential here for a drag and drop IDE editor where the over all app can be architected and generated.

I feel some need for code examples as well [as other commenters], but I'm afraid the post would be bloated with them. Maybe, it's worth expanding that into a series of posts - one per architecture/approach.

Another idea to improve expressiveness of the post would be to draw e.g. ol'good MVC pattern for comparison. But since your article is targeted for people familiar with the subject, that piece of advice might be not very useful.

As for conclusion, I think I cannot completely agree. It seems for me a little like a "silver bullet" solution. On top of that, looking at charts, I can think about a potential problem. Proposed solution requires a lot of internal wiring, which can result in a bunch of glue code.

I think that different solutions suit different application patterns. E.g. ones go well with -bacon and cheese- unconnected models/stores, the others benefit from centralized data hub.

You've started a really interesting topic, but we need to go further. We can benefit more from a deeper analysis.

Otherwise, thanks for this great and very inspirational post