News for hackers. Stuff that matters.
Re:Base84 deserves a place in file names by LoganDark on Sunday September 13, 2026 @12:06PM (#49685531)
macOS has a case-insensitive filesystem by default too.
Re:Base84 deserves a place in file names by tobyhinloopen on Sunday September 13, 2026 @01:30PM (#49686363)
And don’t you dare changing it unless you like random bugs
Re:Base84 deserves a place in file names by applfanboysbgon on Sunday September 13, 2026 @01:39PM (#49686461)
Sell me on this. Why would you want to change it? What good can actually come of allowing foo and Foo to coexist in the same directory?
Re:Base84 deserves a place in file names by hn993302 on Sunday September 13, 2026 @04:15PM (#49688228)
Why: Some things rely on case-sensitive. I don't like it, but they do.

Why not: Some other things (famously Photoshop CS6) rely on case-insensitive.

Any Mac user who's been through enough random adventures probably has a case-sensitive RW disk image lying around for this reason.

Re:Base84 deserves a place in file names by rcyeh on Sunday September 13, 2026 @09:37PM (#49690773)
TIL that MacOS `pwd` has `-P` and `-L` options.

     -L      Display the logical current working directory.
     -P      Display the physical current working directory (all symbolic links resolved).
     If no options are specified, the -L option is assumed.
In your example, using `-P` will show `Cased`.
Re:Base84 deserves a place in file names by jech on Wednesday September 16, 2026 @06:34AM (#49724463)
> TIL that MacOS `pwd` has `-P` and `-L` options.

Interestingly, it wasn't designed to deal with case, but to select whether to resolve symbolic links:

    $ cd /tmp
    $ mkdir a
    $ ln -s a b
    $ cd b
    $ pwd && pwd -P
    /tmp/b
    /tmp/a
Re:Base84 deserves a place in file names by ButlerianJihad on Wednesday September 16, 2026 @06:39AM (#49724507)
In Bash and many modern POSIX shells, `pwd` is a builtin, not to mention an environment variable ${PWD}, but the POSIX system should also provide an external command, such as `/bin/pwd` that would operate on the filesystem, rather than semantically tracking your shell activity.

https://manpages.ubuntu.com/manpages/stonking/man1/pwd.1.htm...

Re:Base84 deserves a place in file names by retrac on Sunday September 13, 2026 @02:02PM (#49686760)
Practically? Quite a few codebases from *nix systems rely on the case sensitivity. To do a successful git clone you need a file system that handles both Makefile and makefile, or whatever.

I ran into it more than once back in the day when I used Mac OS X as my primary OS.

More generally -- case sensitivity is a conceptual nightmare in the Unicode era. Should Cyrillic or Greek be case-insensitive as well? Etc. Do you really want the full complexity of Unicode string handling in your file system?

I would suggest treating file names like raw bytes. On modern Linux, anything but NUL is valid.

Re:Base84 deserves a place in file names by IsTom on Sunday September 13, 2026 @05:35PM (#49688967)
> anything but NUL is valid.

And slash/!

Re:Base84 deserves a place in file names by LoganDark on Sunday September 13, 2026 @01:41PM (#49686501)
It can be nice to checkout some Git repositories that have this. It can also be nice to catch miscapitalizations of filename imports when those would fail on Linux, etc. One of my past workplaces actually had that problem, they mis-cased imports and the product failed to build on Linux. Nobody caught it because they all used macOS or Windows, I was the first to try WSL (this was before I switched back to Mac)

You would be asking for a world of hurt to put your root filesystem in a case-sensitive volume though. All sorts of software and applications have silently relied on case-insensitivity for decades. You can sometimes fix it on a case-by-case basis, but sometimes you can't, and it's also annoying for it to happen in the first place. Better to have a separate case-sensitive volume just for the stuff you want to be case-sensitive.

Re:Base84 deserves a place in file names by ErroneousBosh on Sunday September 13, 2026 @02:30PM (#49687120)
They are completely different words. Why should they be used to mean the same thing?
Re:Base84 deserves a place in file names by tobyhinloopen on Monday September 14, 2026 @01:19AM (#49692302)
Well, so you can base84 encode your filenames for example. (Jk)

My main concern is the loose matching that comes with it where you can refer to any file or folder using any case without issue

Re:Base84 deserves a place in file names by dwedge on Monday September 14, 2026 @04:43AM (#49693749)
Mostly consistency in knowing that Foo will become foo. This is a problem when it comes to (for example) supporting devs on Windows working on a codebase with prod on Linux. The database dbCustomer would be renamed dbcustomer on Windows.

There are workarounds, and containerization is a better idea, but you asked why you might want this.