Yes, exception handling with Observables, just like with Promises, gets to be a bit more complicated, especially as browser Dev Tools haven&#x27;t quite caught up to them yet. (With Promises native to ES2015 that&#x27;s getting fixed and native Observables are tentative for ES2016 or ES2017 which would be great. Also, now that Promises are native, I&#x27;m really hoping for a big Node push towards more Promise-friendly APIs.)<p>The great thing about Observables, though, is that even though exception handling is more complicated as you first learn it: it&#x27;s a lot more <i>consistent</i> as you get used to it than the callback&#x2F;event-handler world. That said, I do think Cycle swallowed exceptions it shouldn&#x27;t have early on (especially without good browser dev tools support) and seems to be getting better at console.loggging them if not propagating them through observable streams as sometimes it should.<p>My fallback is still Knockout as well. It has served its role, with its very basic observables, very well over the years.