> In terms of practical mobile development, the asynchronicity you're dealing with is mostly network operations which execute exactly once per page. Absolutely

> In terms of practical mobile development, the asynchronicity you're dealing with is mostly network operations which execute exactly once per page. Absolutely not true, I have been dealing with a lot of "simple" apps and always once you start introducing stuff like Push Notifications that trigger actions, websockets that send and receive messages and other "unexpected" messages to handle the traditional MVC methods just fall apart. Having said that you can do pretty similar stuff without introducing RxSwift into your application. With or without it, getting these entangled multi-source event handling mechanisms to work well takes a really disciplined approach.