[bsaul]

hi, thanks for sharing. one question though : to me, the hardest and most convoluted api in cocoa isn't related to model handling but to the view : doing simple things like a tableview reload immediately followed by a scroll, or animation composition when updating data always is a problem because the way uikit elements work internaly is quite opaque ( and the fact that there are three orthogonal api to position a view don't help).

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..