I used ReactiveCocoa in this example. Actually at the time I wrote this article, there was only a thin Swift API above the Objective-C codebase of the framework and it helped a lot to see it working from Swift. I referenced the updates in the first lines of this article, since ReactiveCocoa has been changed a lot since. They have a completely different API for Swift now, with conceptual changes compared to the original Objective-C versions (up until 2.x).
There are several differences between RxSwift and the current ReactiveCocoa by design. I haven’t used RxSwift in a real project yet, but I understand that choosing from these two kind of depends on which concept is closer to your mind. And of course if you’ve done work with Rx in other languages its official Swift port RxSwift should be easier to understand. You can find a great explanation about the differences here: http://stackoverflow.com/questions/32542846/reactivecocoa-vs-rxswift-pros-and-cons