Right, but isn't it so that FRP is especially well suited for describing state machines in a more DRY (concise) way?
I mean state machines can be described/encoded by state transition tables or by some kind of higher level functions.
For example, say I have a state machine where the possible inputs are the digits 1 to 10 and we have two states, A and B. The rule for transition is that if the sum of the last ten inputs digits is prime then we transition, otherwise not.
Anyway, maybe this is not the best example, but I was just wondering what would be a good example where FRP would shine, in contrast to more traditional approaches (for example UML statecharts).
What would be a good example/problem that would be easier/more concise/more elegant/ more DRY to describe/define/reason about using FRP than UML statecharts (the traditional/mainsream way) ?
How would the reactive petrol pump compare in this respect (for example) ?
What class of ( reactive ) problems can be "better" described with FRP than with statecharts/UML ?