Yes, when I first read about Flux (which was after I learned RxJS) I kept thinking that you are essentially writing by hand things that could be generated automatically. It&#x27;s like going from nested callbacks in early Node.js to Go. :)<p>I prototyped a decent amount of UI in Cycle and thought that it was great. Using virtualdom with it was really enjoyable and a lot easier to reason about than what is seen in the typical JQuery-based RxJS&#x2F;Bacon&#x2F;Kefir examples. However, I found the interaction between exception handling in Cycle and RxJS to be strange at times... maybe I&#x27;m just not experienced enough with them yet, but I swear I had some swallowed exceptions that I could never track down. That being said, I feel that this is &quot;the future&quot; (standard disclaimer applies).<p>Currently I&#x27;m using Knockout.js for UI stuff at work and I&#x27;ve found that by maximizing the use of pure computed observables and minimizing mutation of observables (essentially, implementing unidirectional data flow) I can get pretty good results.