Earlier quoted context omitted.
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.
More problematic is that many case insensitive hard drives would be copied into new machines and there would be millions of conflicts. Some utility would have to sit there and annoy people by asking them to make decisions.
Apple File System
91–100 of 406 posts
Re: Apple File System
#92I hope they don't patent it and go after Linux implementations, as Microsoft did with exfat.
If you sue closed technology you get burned. I didn't have a problem with Microsoft doing what they did. We should have used an open file system for those devices. I personally have used ext2/rfs on my drives and it is a pretty light security system ;)
Re: Apple File System
#93No checksumming?
Re: Apple File System
#94Earlier quoted context omitted.
I also didn't see any mention of compression. Hopefully those are at least being worked on and just didn't make it into the docs yet.
HFS+ already supports compression and it says APFS would support nearly all of the features of HFS+ , so there's hope.
Re: Apple File System
#95Any guess if AFS is written in Swift?
https://en.wikipedia.org/wiki/I/O_Kit http://opensource.apple.com/source/xnu/xnu-3248.20.55/iokit/
Re: Apple File System
#96It would be really nice is there was a modern file system that "just worked" regardless of device. I'm tired of having exFAT/FAT being the only filesystem I can reliably use on multiple different OS-es painlessly, and even then I can't use it for all the functions of those OS-es (No time machine). Hopefully this will be open enough to enable that, though who knows how it will shake out.
Re: Apple File System
#97> Flash / SSD Optimization I.e., a "unique copy-on-write design" > Space Sharing Basically, ZFS datasets. > Snapshots If those can be sent: Finally Time Machine done right. > The AFP protocol is deprecated and cannot be used to share APFS formatted volumes. Interesting. > An open source implementation is not available at this time. Apple plans to document and publish the APFS volume format when Apple File System is r…
> If those can be sent: Finally Time Machine done right.
If this ends up being true I can't wait—it's so frustrating watching tiny incremental backups take forever over the network. It seems like "Preparing" and "Cleaning up" take longer than moving the data.
Re: Apple File System
#98Complain 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
We detached this subthread from https://news.ycombinator.com/item?id=11897039 and marked it off-topic.
Re: Apple File System
#99Earlier quoted context omitted.
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.
For the end-user they could prevent duplicate different-cased file names in the UI layer (the Finder), instead of the file system. That would be a more appropriate place for it anyway.
Re: Apple File System
#100Earlier 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.