Wish I knew what frameworks and system calls are? Can you specify an action these take that might be blocked w AFPS?They might. Applications that target lower-level APIs or system calls could run into problems. Apps that mostly stick with Apple’s frameworks, will probably not have any problems.
I don't understand why no one is talking about this coming tsunami. I have an entire notebook full of useless powermac cds. Is Apple about to drop another atom bomb on all our software?Unless something has changed recently, APFS is completely case-sensitive, much like Linux filesystems.
Files named "test" and "TEST" can coexist, where on the old case-insensitive HFS+, they could not.
Adobe has long not supported their apps on case-sensitive filesystems, for weird legacy technical-debt and laziness reasons.
iOS is not concerned with this change, since it has always used HFSX, which is a case-sensitive variant of HFS+.
Long story short, you're most likely going to have a bad time getting your old Adobe apps running on macOS 10.13 and such.
Adobe is probably in a panicked rush to get Creative Cloud 2018 working properly on case-sensitive APFS, and there will be much public outcry against both Apple and Adobe for putting people in a difficult upgrade situation.
From what I understood, the rules that HFS+ uses to make filenames case-insensitive, are pretty byzantine.I would be amazed if Apple doesn't offer a case-insensitive option before making it the default filesystem.
This article here is a good read: http://drewthaler.blogspot.co.uk/2007/12/case-against-insensitivity.html. It claims that the case-insensitive implementation of HFS+ is not just faulty/limited but also outdated, and that this is chronic and unavoidable for file systems of this kind. I was not leaning in either direction, but I found this article pretty persuasive.Interesting, but at the same time I'm not aware of any fundamental reason why there can't be simplified case-insensitivity. Many European languages have trivial rules around this, and while I'm mostly not familiar with other languages I suspect that in many cases they can be kept case-sensitive without breaking much (for example, HFS+ is already kanatype-sensitive for Japanese).
That's a very sensible argument.Yes, Aunt Tillie will think that "Muffin Recipe.rtf" and "muffin recipe.rtf" ought to be the same file. But you know what? She'll also think that "Muffin Recipe .rtf" and "Recipe for Muffins.rtf" and "Mufin Recipe.txt" ought to be the same file too.
-i | --allow-case-insensitive Convert case-insensitive HFS volumes to case-insensitive APFS volumes. Without this flag, all converted volumes will be case-sensitive.
Disk Utility and Finder are confused about volume type after conversion, stating the volume is "APFS (Case-insensitive)" when it's obviously case-sensitive as demonstrated by actions on files in Terminal.Interesting find. Though note the phrasing: ‘without this flag, all converted volumes will be case-sensitive’. This means that a conversion from case-insensitive to case-sensitive is not only provided, but also the default. This can imply that case-insensitivity is something to be opted into.
You should have a look at the link I posted above, it touches upon this argument. It also explains some of the technological challenges.I'd have to think that internally, Apple is not sure what to do about this. "Normal" users may very well freak out when faced with files named "Budget" and "budget" coexisting. It's hard to convince people that case-sensitivity is a "good thing".
I am not sure about that. If they are contemplating a switch, then having a (transitional) alternative is something they might want to offer. From what I understand, APFS is going to replace HFS+ completely in a short timeframe. It makes sense to me that Apple would offer a case-insensitive variant for external drives or disk images to lessen the blow for people who absolutely must have a case-insensitive option for the time being.The fact that a case-insensitive option is now available makes me think the case-sensitive side at Apple is losing its arguments.
Are case-sensitive volumes still identified as simply ‘APFS’? That would also be a difference, because currently it is the opposite.Disk Utility and Finder are confused about volume type after conversion, stating the volume is "APFS (Case-insensitive)" when it's obviously case-sensitive as demonstrated by actions on files in Terminal.