this post was submitted on 06 Sep 2024
615 points (90.6% liked)

linuxmemes

20880 readers
2 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 33 points 2 months ago* (last edited 2 months ago) (2 children)

This isn't "Windows design"... this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.

NTFS is case sensitive in its underlying design, but was made case insensitive by default, yet case preserving, for reasons of backwards compatibility.

If Microsoft has to design something from scratch, without the need for backwards compatibility, they go for case sensitive themselves. For example: Azure Blob Storage has case sensitive file names.

[–] [email protected] 6 points 2 months ago (1 children)

If you rename a file only changing the casing it doesn't update properly, you need to rename it to something else and back.
This is so userfriendly I have been stumped by it multiple times.

On the other hand in using Linux I have had a number of problems with the casing of files: The number is 0

[–] [email protected] 6 points 2 months ago

If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back. This is so userfriendly I have been stumped by it multiple times.

To my great surprise, this has been fixed. I don't know when, but I tried it on my Windows 10 VM and it just worked. Only took them 20 years or so :)

[–] [email protected] 2 points 2 months ago

case insensitive by default, yet case preserving

This isn't just a Windows thing... It's the same on MacOS by default.