State is hell when working with asynchronous code. Trying to deal with realtime data and user interaction with callback after callback after callback quickly leads to madness. Any callback, called at any time, can modify application state making code complex and hard to reason about.
I'll introduce both FRP and Bacon - and with visualisations and examples show just how tasty Bacon is for working with asynchronous code.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?