Editing Case sensitivity (section)

==In filesystems==
In filesystems in [[Unix-like]] systems, filenames are usually case-sensitive (there can be separate readme.txt and Readme.txt files in the same directory). [[MacOS]] is somewhat unusual in that, by default, it uses [[HFS Plus|HFS+]] and [[APFS]] in a case-insensitive (so that there cannot be a readme.txt and a Readme.txt in the same directory) but [[Case preservation|case-preserving]] mode (so that a file created as readme.txt is shown as readme.txt and a file created as Readme.txt is shown as Readme.txt) by default. This causes some issues for developers and [[power users]], because most file systems in other Unix-like environments are case-sensitive, and, for example, a source code tree for software for Unix-like systems might have both a file named Makefile and a file named makefile in the same directory. In addition, some Mac [[Installation (computer programs)#Installer|Installers]] assume case insensitivity and fail on case-sensitive file systems.

The older [[MS-DOS]] filesystems [[FAT12]] and [[FAT16]] were case-insensitive and not case-preserving, so that a file whose name is entered as readme.txt or ReadMe.txt is saved as README.TXT. Later, with [[VFAT]] in [[Windows 95]] the FAT file systems became case-preserving as an extension of supporting [[long filenames]].<ref>{{cite web|url=https://technet.microsoft.com/en-us/library/cc739978(v=ws.10).aspx |title=Case Sensitivity in Subsystem for UNIX-based Applications |work=Microsoft Learn |date=2005-08-22 |access-date=2013-05-20}}</ref> Later Windows file systems such as [[NTFS]] are internally case-sensitive, and a readme.txt and a Readme.txt can coexist in the same directory. However, for practical purposes filenames behave as case-insensitive as far as users and most software are concerned.<ref>{{cite web|url=http://support.microsoft.com/kb/100625 |title=Filenames are Case Sensitive on NTFS Volumes |work=Microsoft Support |date=2006-11-01 |url-status=dead |archive-url=https://web.archive.org/web/20130723020137/http://support.microsoft.com/kb/100625 |archive-date=Jul 23, 2013 |access-date=2013-05-20}}</ref> This can cause problems for developers or software coming from Unix-like environments, similar to the problems with macOS case-insensitive file systems.