title: ReactiveCocoa vs RxSwift - pros and cons?
body: <p>So now with swift, the <a href="https://github.com/ReactiveCocoa/ReactiveCocoa">ReactiveCocoa</a> people have rewritten it in version 3.0 for swift</p>
  
  <p>Also, there's been another project spun up called <a href="https://github.com/ReactiveX/RxSwift">RxSwift</a>.</p>
  
  <p>I wonder if people could add information about what the differences in design/api/philosophy of the two frameworks are (please, in the spirit of SO, stick to things which are true, rather than opinions about which is "best")</p>
  
  <p>[Note for StackOverflow mods: This question DOES have definitive answers, the answer is the differences between the two frameworks. I think it is also highly on topic for SO]</p>
  
  <p>To get started, my initial impression from reading their ReadMe's is:</p>
  
  <ul>
  <li>As someone who is familiar with the "real" C# Rx from microsoft, RxSwift looks a lot more recognisable.</li>
  <li>ReactiveCococa seems to have gone off into it's own space now, introducing new abstractions such as Signals vs SignalProducers and Lifting. On the one hand this seems to clarify some situations (what's a Hot vs Cold signal) but on the other hand this seems to increase the complexity of the framework a LOT</li>
  </ul>