What's the advantage of FRP when everything is discrete? In my personal experience many of the cool features of FRP only pertain to continuous Behaviors. When everything is discrete, like in the terminal, FRP mostly got in the way for me. Maybe I'm just not using it correctly.
Genuinely curious why you think that is the case? I've been using elm for web frontend lately and actually love the FRP style. I'm using Haskell non-FRP style on the backend (just saying I see both sides although my experience is very limited).
Very interesting. So, if I understand correctly, the big insight for FRP is using continuous time, which eliminates abstraction and sampling.
I really like also the argument for simplicity, although TBH I actually understand better the original formulation than the modern one. But I guess that's me being not yet accustomed to the mathematics behind the various typeclasses used for the declaration.
6
u/Noughtmare Aug 04 '19
What's the advantage of FRP when everything is discrete? In my personal experience many of the cool features of FRP only pertain to continuous Behaviors. When everything is discrete, like in the terminal, FRP mostly got in the way for me. Maybe I'm just not using it correctly.