Be the first to like this
ReactiveCocoa is the first and most commonly used implementation of the reactive paradigms in Cocoa, with a lot of bindings to UIKit/AppKit frameworks to help connecting reactive signals to UI elements. I was lucky to work on a huge Objective-C codebase with heavy use of ReactiveCocoa prepared to be released for millions of users, so I have some pros and cons in my pocket even for that scale. I'd like to discuss the state of ReactiveCocoa in 2016, to help people to understand their possibilities especially if they are in the phase of moving to Swift. I'd like to share the main differences of the new ReactiveCocoa Swift API with code snippets. What are the conceptual changes, in comparison to the v2 Objective-C API. Some examples of other libs, like RxSwift and what are the main differences in usage.