As I understand it, the point of the presentation was highlighting the incidental complexity arising from the implicit instability of mutable state. If an immutable snapshot of the whole program state was an implicit parameter to functions, that wouldn't be so bad. It's the fact that anything can pull out the rug from under your feet at any time that creates the need for paranoid constructs in most classical concurrent programming.