You can have a machine where you are actually more free to experiment than simply being unrestricted. If you have a machine where you can roll back changes to a saved point, you are more free to experiment, even with dangerous and esoteric mechanisms. This is what we had in Smalltalk. Smalltalk used to be an OS. (There are 4 hooks in the old Smalltalk-80 image for lifting the drive head, putting it down, and moving it in and out.) When I used it, it was no longer an OS, but this is how I know that doing
Semaphore allInstances do: [ :each | each release ]
Locks up your image so hard, there's often lag when you try to kill the VM process. I can do that with un-checked in code in the image, then restart from a saved image, replay all of my actions from the change log except for the last one, and I'm back in seconds, all of my code nice and safe.This degree of rollback ability would also be great for simplifying parental IT. You'd need to add some sort of cloud storage for storage of authentication secrets and the most important data, but then it would be almost bulletproof.