Earlier quoted context omitted.
Will they deploy it case insensitive, still?
Presumably as with today, you'll have the option. I don't have a strong opinion on case sensitivity of file names, but I suspect they'll keep it case insensitive by default. I think for the average non-technical user that two files, "MyFile.txt" and "myfile.txt", being different could lead to some confusion, and Apple historically has apparently considered that confusion unacceptable.
Apple File System
81–90 of 406 posts
Re: Apple File System
#82Earlier quoted context omitted.
Copy-on-write and snapshots are excellent building blocks for Time Machine, so much in fact that, when it was announced, I suspected it was because of ZFS (which, at the time, was being considered for OSX). It's very likely TM will be adapted to work on it (with about 20 lines of code)
I'm not sure about snapshots, TM is made to work by just copying the directory structure over, and each backup is a fully functioning hierarchy. But cloning is definitely a big deal.
Re: Apple File System
#83Re: Apple File System
#84Earlier quoted context omitted.
Will they deploy it case insensitive, still?
Presumably as with today, you'll have the option. I don't have a strong opinion on case sensitivity of file names, but I suspect they'll keep it case insensitive by default. I think for the average non-technical user that two files, "MyFile.txt" and "myfile.txt", being different could lead to some confusion, and Apple historically has apparently considered that confusion unacceptable.
Re: Apple File System
#85Re: Apple File System
#86Complain if you want, but you seem to forget that it is from Apple. And that makes it somehow better with magical goodness that nobody else could attain. Apple's engineers are not mere humans like every other 'ordinary' tech company would hire. /s
I don't know about that, but there is definitely something magical about these keynotes that makes Apple haters come out of the woodwork.
Re: Apple File System
#87With Space sharing and multiple logical volumes there will probably be a shift to encrypting users home directories separately.
Probably even an unencrypted System Base, which is read-only and protected by rootless anyway, so the system can boot without user interaction.
This also finally allows the most user friendly implementation of file encryption: Encrypted Folders, supported by the OS.
Sounds cool, Id be willing to help with a rust port once the source is available :) (case sensitive only - naturally)
Re: Apple File System
#88Re: Apple File System
#89Earlier quoted context omitted.
Will they deploy it case insensitive, still?
Presumably as with today, you'll have the option. I don't have a strong opinion on case sensitivity of file names, but I suspect they'll keep it case insensitive by default. I think for the average non-technical user that two files, "MyFile.txt" and "myfile.txt", being different could lead to some confusion, and Apple historically has apparently considered that confusion unacceptable.
Re: Apple File System
#90Earlier quoted context omitted.
Copy-on-write and snapshots are excellent building blocks for Time Machine, so much in fact that, when it was announced, I suspected it was because of ZFS (which, at the time, was being considered for OSX). It's very likely TM will be adapted to work on it (with about 20 lines of code)
I'm not sure about snapshots, TM is made to work by just copying the directory structure over, and each backup is a fully functioning hierarchy. But cloning is definitely a big deal.