June 21, 2026
Slash fiction, but for folders
A tale of two path separators
Mac users just rediscovered that slashes are fake and the comments got gloriously weird
TLDR: macOS still secretly translates between two different file path styles, so a file name can appear with a slash in one place and a colon in another. Commenters were split between nostalgic old-school Mac lore, jokes about even weirder systems, and frustration that Apple is still dragging this legacy around.
Apple fans got a fresh dose of filesystem chaos this week after a blog post reminded everyone that on macOS, a file can look like it has a slash in its name in Finder, while the command line shows a colon instead. In plain English: your Mac is basically wearing two name tags at once, thanks to old Apple history colliding with Unix, the family of systems modern Macs partly came from. It’s a weird compatibility trick that has survived all the way from classic Mac days to today’s Apple File System.
And the comments? Absolute gold. One camp showed up like digital war veterans, explaining that old Macs were even stranger than the post suggested. Commenters reminisced about paths starting with colons, double colons meaning “go up a level,” and the general feeling that vintage Apple path rules were less “computer system” and more ancient rune magic. Another group was baffled that Apple still carries this around at all, asking the obvious spicy question: is this still smart design, or just decades of inertia nobody dares touch?
Then came the comedy relief. One commenter escalated immediately: what if an operating system had no folders at all? Another wandered in hoping for the legendary ¥ path separator plot twist instead. The overall vibe was a mix of nostalgia, disbelief, and mild horror: people weren’t just reacting to a quirky bug-like feature, they were reacting to the realization that modern Macs are still quietly haunted by decisions made before many users were born.
Key Points
- •macOS can display filenames with apparent slashes in Finder while command-line tools like `ls` show corresponding colons.
- •The behavior comes from macOS supporting two historical path separators: slash from Unix and colon from classic Mac OS.
- •This dual behavior reflects the merger of classic Mac OS and NeXTSTEP file system conventions, including HFS+ and UFS compatibility.
- •A 2000 USENIX paper by Apple engineers describes a translation layer that can present colon characters as slashes in some application contexts.
- •Apple replaced HFS+ with APFS in 2017, but the dual path-separator behavior still exists in modern macOS.