| > It is/was on some (but not all) other platforms, but not on macOS. I know why it's there. As I wrote in another post, this was a great choice in the 128KB/floppy days of the early macs. It no longer is - for the general user, on a computer (unlike a car) it feels like a distinction without a difference. The fact that it is consistent and based on consistent logic (albeit one that was prescribed 30 years ago) does not matter, IMO. > Regarding the view state, Linux and Windows do this for the local machine, where as macOS does it for the directory. I think you're rationalizing a poor design choice. For local files, the end result is mostly the same (except Linux preserves the directories mtime) -- as local files are rarely if ever accessed across the network by someone with write permissions for that directory. And those permissions often make it seam dysfunctional on a shared directory - you can't store settings, so it doesn't stay the same between visits. How does your explanation sit with the fact that there's a way to disable this for network/remote directories, but not for local ones? > and macOS has this as well via autofs if you want it -- it's built in I'm aware that's a power-user preference, I couldn't figure out how to do it on the mac; I'll look up autofs permissions - any recommended documentation? |