I'd like to add to the other replies that first-class i/o is less about "papering over" side effects, and more about reining in exactly where side-effects can occur, the kinds of side effects that are allowed, and requiring a full enumeration of possible outcomes (resource exhaustion, you don't have permission, etc). Kind of like checked exceptions, in a way.