Earlier quoted context omitted.
it's the second time this week i hear about reactive cocoa.I'm starting to hate uikit with a passion, but what's so special about it ?
iOS engineer who worked on the Fabric app here :) I gave a talk about this topic at a Swift conference last year, if you wanna check that out! https://www.youtube.com/watch?v=Ent6LJDIB3I
So the fact that reactive cocoa tries to hide the notion of state transition makes me wonder how you can then deal with UIKit views animations api ( collection flow animations or tableview begin updates, no to mention view controllers interactive transitions).
I've wondered if using a future based api for view animations wouldn't be a solution..