Re: Xcode 9

That logic sounds flawed. Going from case insensitive to case sensitive cannot result in a conflict since insensitive is the broader instance and would already have prevented the conflicts. I don't know the rationale for Apple to change but potential collisions cannot be it. 

> On Sep 27, 2017, at 9:30 AM, Tim Jones <[email protected]> wrote:
> 
>> On Sep 26, 2017, at 8:55 PM, Bernd Fröhlich <[email protected]> wrote:
>> 
>> Jon Ogden :
>> 
>>> That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??
> 
> Because the would have beaus coups issues updating a system where changing from case insensitive would result in probably file collisions during the upgrade.  APFS as the default only on SSDs was always the plan as it was designed for the newer Mac systems - which are all SSD.
> 
>> It´s not a bug, it´s the same feature as with HFS+. You can choose what you want.
>> 
>> Here is the official answer:
>> <https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html>
>> 
>> "APFS, like HFS+, is case-sensitive on iOS and is available in case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default."
> 
> And that stand is a change from the original design of APFS - it was originally released as case-sensitive only.  It was changed after major companies whined about how that would break there apps.
> 
> Coming from the Unix world (of over 34 years), we're used to case sensitive environments, so all of our apps check this regardless of what the filesystem allows.  It really is the smarter way to handle a filesystem.
> 
> --
> Tim
> 
> 
> 
> To unsubscribe, email [email protected]
> 


To unsubscribe, email [email protected]