I'm sorry, but I just don't see that there's "something to be said". It seems like a lot of error-prone work for no gain.

Error handling is already a big part of my life - I don't need this huge body of repetitive, mostly meaningless error code to make my job harder.

More, it makes any sort of functional approach doomed to fail if each function call has to have an error check.

EDIT: and I want to obscure repetitive, uninformative parts of my program! I don’t want to have to know the details, except when they are important.

Nearly all the time, when I write code, I just want error to propagate right through that code unchanged.

I am notoriously obsessive about error handling, and yet in my current project, in 7150 lines of code, I only catch exceptions 36 times, which is about once per 200 lines of code.

More, reading through of these, each of these is important in some way.

Once I’m just catching one error and throwing a clearer one. Most commonly, I try to do something, expecting to fail sometimes even in correct operation, and then try something else. I have a single place I catch all errors from the CLI and give them some love.