[legulere]

Rule 1 of software development should be: Never blame the user, when the situation could have been avoided through code.

Especially in this case. Isolation has been one of the main drivers of operating systems. Isolation between users, so they can't change each other's files etc. maliciously . Isolation between processes, so they don't accidentally corrupt each other. At least since the first computer virus in the wild in 1982 it should have been clear that software can also potentially be malicious and needs to be isolated from having the same rights as the user executing it.

The only reason why executing arbitrary x86 code in ring 3 is dangerous are the syscall interfaces the operating systems offer.

[perspectivep]

Which is why UWP has a capabilities-based sandbox.

[talmand]

Sometimes you do have to blame the user though. As an extreme example; if I take a hammer to my computer and when it eventually fails can I blame the faulty hardware?