Yes, but I/O is impure and sequentially dependent, unlike mathematics.

Maybe the "impedance mismatch" between pure-fp and I/O is too great, with the IO monad being the "leaky abstraction" of the FP world.

Then OO is not a bad solution to an irrelevant problem, but a pretty-good solution to a bad relevant problem.

EDIT:

To clarify: The "problem" is change.

Imperative programming relates sequential device-change over time, to sequential programming lines. OO programming is a structured imperative programming.

Pure FP langs model sequential change with (roughly,) lists of actions to-be-performed that are snaked through your program.

(Also: maybe OO's failure has more to do with its limited static analysis, type systems, than its model of change?)