Indeed. That is why you have: at : Behavior α → Time → α which is a pull based continuous data type. This is a very elegant concept but comes with its own set

Indeed. That is why you have: at : Behavior α → Time → α which is a pull based continuous data type. This is a very elegant concept but comes with its own set of difficulties if implemented naively (space and time leaks). A similar concept is shown here: https://www.microsoft.com/en-us/research/uploads/prod/2000/09/pj-eber.pdf https://www.microsoft.com/en-us/research/uploads/prod/2000/0... Imo the main problem in the end is/was that not many problems are that conveniently described as continuous. Discrete and push based (rx) can do most things and even that is overused. It makes problems that are otherwise very hard, much easier to describe and solve using the many powerful combinators https://www.learnrxjs.io/learn-rxjs/operators https://www.learnrxjs.io/learn-rxjs/operators On the other hand you make all those easy problems quite a bit harder and if you are not disciplined you end up with complex rx "queries" that have semantics that you dont understand.