Right but windows also aims to be backwards compatible which means it was trying to run things designed for a single user system undermining protections.
'vim' wasn't designed for multi-user use. Nor was emacs.
Applications don't need to somehow be "designed" for multi-user systems. It's up to the underlying system to enforce application isolation in various ways, which NT has and does.
Does vim expect to be able to delete files in /bin?
If vim tried to create, modify and delete files willy nilly It would quickly run into problems. I would guess vim keeps it's temp files in /tmp and config files in ~/.vimrc?
Windows doesn't/didn't have any of this. If you want to be compatible with lotus123 and lotus123 writes it's tmp files to the root directory, you need to keep it writable, or you break lotus123.
Right but windows also aims to be backwards compatible which means it was trying to run things designed for a single user system undermining protections.
That makes absolutely no sense.
'vim' wasn't designed for multi-user use. Nor was emacs.
Applications don't need to somehow be "designed" for multi-user systems. It's up to the underlying system to enforce application isolation in various ways, which NT has and does.
Does vim expect to be able to delete files in /bin?
If vim tried to create, modify and delete files willy nilly It would quickly run into problems. I would guess vim keeps it's temp files in /tmp and config files in ~/.vimrc?
Windows doesn't/didn't have any of this. If you want to be compatible with lotus123 and lotus123 writes it's tmp files to the root directory, you need to keep it writable, or you break lotus123.
2 replies →