OSDev.org

onlyonemac wrote:

• Application will stop execution momentarily as the next section is read from disk, which could cause problems in a timing-critical section of code
• Loading of application cannot be verified before execution begins as no checksum can be calculated (as data is read on an on-demand basis, so a corrupt application file cannot be detected)
• User may remove disk while application is executing, leading to failure when next section is required

I'm not saying that you are wrong, but when you disagree with the designers of every major operating system you might want to take a little time out to consider why that is the case.

It's the application responsibility to know what it does with the resources it uses. It should check for errors that could have happened due to file/memory corruption .Be they hardware or software.

If your OS can't transmit an error it detected, what if the error was undetected ? like mmaping a badly downloaded file ?