It should be possibly to speculatively execute code that's accessing resources and only allowing transactions on system resources to commit successfully if othe

It should be possibly to speculatively execute code that's accessing resources and only allowing transactions on system resources to commit successfully if other transactions haven't invalidated them. Meaning a process could start loading and reading while queuing writes and only writes would block while another process is locking access to the executable to scan it. If the scan succeeds the writes are committed and if it fails it could revoke execution privileges and all the work is undone. Lot of hand waving there, but when you're not committed to existing file system semantics there is a lot of room for innovation.