The issue is more one of fragmentation; figuring out which file(s) / method(s) are responsible for some item of state can get to be impossible without a powerful debugger, and constantly changing frameworks / libraries don't help.
For a start, one does not persist "local state", and this is a clear give-away:
> state cannot be cheaply recomputed or regenerated like other live values
The author seems to be arguing against a global state encapsulated into a tree of disjoint accessors. And his solution:
> our programs become stateless logics manipulating a stateful substrate
Is verbatim the FP-way of avoiding working on global state.
The issue is more one of fragmentation; figuring out which file(s) / method(s) are responsible for some item of state can get to be impossible without a powerful debugger, and constantly changing frameworks / libraries don't help.