The abstraction of FP, which is the same as mathematics, is that all functions can be treated as resolved instantly in time and from a given starting point you'll always get the same answer.
However in the real world things take time and time flows in one direction, and have a nasty habit of being non linear.
FP abstracts away these complications with the notion of 'actions' which are then dealt with by some outside 'runtime system'.
Yes I know about the IO loop. FP reduces the gap to zero when segregated away from IO.
However I literally said for distributed systems this does not apply. This is IO. If you're referring to something like the DOM, the architecture is similar for redux. Within the bounds of IO your program is not dynamic.
However in the real world things take time and time flows in one direction, and have a nasty habit of being non linear. FP abstracts away these complications with the notion of 'actions' which are then dealt with by some outside 'runtime system'.
Hence System.Time.getClockTime >>= print