Apple's attempts at making "seamless" user experiences can be frustrating, especially on edge cases. For example, in Garageband instruments are stored in special files down a ways in a directory tree in Application Support. It happens that files get corrupted, but access to the file is so abstracted that the source of the trouble is not apparent, as it is a directory not intended to be accessed by the user. It's an attempt to hide complexity from the user but it makes it hard to trouble-shoot, or to perform actions outside of the expected.
The area that does boggle my mind in terms of a flat structure are complex multi-media authoring environments. Where different files and types are used to assemble a larger work.
My main principle as an audio engineer is that I have to know exactly where each file in the project lives in the FS. If I'm not sure, the scenarios in which projects, or parts of projects get lost happen more frequently.
Not to mention that a given project uses many files of different types, and can have 10s or 100s of thousands of files. Automatic file management seems like a recipe for disaster, especially as it won't work perfectly.
The area that does boggle my mind in terms of a flat structure are complex multi-media authoring environments. Where different files and types are used to assemble a larger work.
My main principle as an audio engineer is that I have to know exactly where each file in the project lives in the FS. If I'm not sure, the scenarios in which projects, or parts of projects get lost happen more frequently.
Not to mention that a given project uses many files of different types, and can have 10s or 100s of thousands of files. Automatic file management seems like a recipe for disaster, especially as it won't work perfectly.
I don't get it.