To me this is backwards. I don't think there is a common need to handle a generic file not found error. Let's say the user tries to open an image file. The imag

To me this is backwards. I don't think there is a common need to handle a generic file not found error. Let's say the user tries to open an image file. The image file exists, but when decoding the image file you need to open some config file which happens to be missing. That needs entirely different handling than if the image file itself was missing. Though, I suppose with something broader like IOException the situation is different. try { open file read some bytes read some more bytes } makes sense, as they all relate to the same underlying resource being in a good state or not.