Learning Cycle.js — Two months later

Right on

RxJS Observables are generally cold. This means that two different calls to subscribe() will generate two separate side effect free executions of the Observable. Hot, on the other hand, is when different calls to subscribe() may share the same execution of the Observable.

Understanding the difference between hot and cold Observables was key for me to be able to scale my code and was by far the biggest learning challenge I've faced during these two months.


Even though Cycle.js, RxJS or Reactive and Functional programming in general have a pretty steep learning curve, I still firmly believe that these tools and frameworks provide a much stronger abstraction and paradigm than the ones we're usually more familiar with (imperative and object-oriented). Being able to restrict and control side effects is key to building flexible, loosely-coupled and scalable systems. Cycle.js still demonstrates me that it has a lot of potential and with the introduction of xstream it might become even easier and enjoyable to work with.



Brazilian, Gaúcho and Software Engineer at Stripe

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store