Maybe I didn't understand this article properly, but is it suggesting suppressing ALL filesystem related errors rather than handling them properly? OK I get th

Maybe I didn't understand this article properly, but is it suggesting suppressing ALL filesystem related errors rather than handling them properly? OK I get that PHP doesn't support atomic operations, but there are so many different errors that could happen when working with files. Say a permissions error, if the permissions of the file were changed between it being created and deleted that's an issue that needs resolving before your tmp folder fills up, it's easy enough to fix and should be reported as an error (be it to the front-end or to a backend logging service). Surely there is a better way to handle these race conditions without just ignoring all filesystem related errors.