I have criticisms of FRP implementations, but the supposed two fatal flaws proposed here seem wrong. 1: Static type support for causality. If this is referring

I have criticisms of FRP implementations, but the supposed two fatal flaws proposed here seem wrong. 1: Static type support for causality. If this is referring to what I think it is, then it's something normal async code doesn't have to begin with. 2. Memory leaks: these are mostly symptoms of lazy programming a la Haskell, not about FRP. Once you eliminate this bug of Haskell's, the significant ones go away. For avoiding them in practice, try FrTime (scheme), Flapjax (javascript), and Rx's "hot" streams (most languages). Edit: for those proposing tasks, that's about something different. The loose answer to tasks are promises. FRP is about a more expressive (multiple assignment scenario) and structured (more synchronized) promise.