I was learning Git. Minding my own business. Running commands quietly, like a person with no particular agenda. Then I ran this:
git config --list --local
Output:
core.ignorecase=true
That tiny setting made me ponder, Why does Git even need to care about case?
Case Sensitivity 101
It turns out the answer sits at the level of the filesystem itself. MacOS (HFS+, APFS) is case-insensitive, but case-preserving. You create File.txt, attempt file.txt afterwards, and macOS treats them as the same entity, while remembering which capitalisation you preferred. Linux is case-sensitive. File.txt and file.txt are two entirely distinct files, with no opinion about each other whatsoever. Git's core.ignorecase=true flag exists to prevent repositories from detonating when developers switch between the two. A small flag carrying considerable weight.
A Detour into Apple Filesystems
One question, as tends to happen, led to another. I found myself reading about HFS+, Apple's old filesystem, a relic of the late 1990s, kept alive well past its natural lifespan through what can only be described as determined engineering stubbornness. Then, in 2017, Apple released APFS Apple File System designed specifically for SSDs. Built for this century.
The difference was considerable.
What APFS Actually Does
- Space Sharing → One container, multiple volumes, sharing a single pool of storage rather than each claiming a fixed partition.
- Copy-on-Write (CoW) → Modified data is written to a new location before the old is discarded. The filesystem never overwrites live data. Corruption from incomplete writes becomes structurally improbable..
- Snapshots → The system can capture its own state at a point in time and return to it precisely. This is what Time Machine is, at its core — not magic, but snapshot management made approachable..
- Clones → Duplicate a file instantaneously. The copy consumes no additional space until the two versions actually diverge.
- Atomic Safe Save → A file either saves completely or does not save at all. There is no intermediate state in which a half-written file can corrupt your data.
- Multi-Key Encryption → Different files can carry different encryption keys. The security model becomes considerably more granular than a single master key over everything.
The Takeaway
I began by examining a Git configuration flag. I arrived at filesystem architecture. This is, I have come to accept, simply how curiosity operates. One honest question rarely stays alone. And regarding APFS, I will give credit where it is due. Apple built something genuinely well-considered here. My MacBook Pro M4 may have been priced as though it were assembled by hand in a Swiss watchmaking atelier, but knowing the engineering underneath makes it, marginally, more forgivable.