Designing Windows 95’s User Interface

Re:Designing Windows 95’s User Interface by lloydde on Wednesday February 07, 2018 @10:15AM (#16324893)

Case-preserving,case-insensitive is good for less sophisticated users: prevents accidentally misplacing or duplicating files with capitalization; and simplifies through this constraint media listing and sorting — no worrying about jpg vs JPG.

What are the use cases that bother you?

[ Parent | on HN ]

Re:Designing Windows 95’s User Interface by Retra on Wednesday February 07, 2018 @08:52PM (#16329560)

When a file refuses to rename because the OS thinks it is the same name. When you have multiple files that differ in case, but they overwrite each other because the OS thinks they are the same.

Really, the only place case-insensitive filenames makes sense is when you are searching. It makes no sense for any other reason.

[ Parent | on HN ]

Re:Designing Windows 95’s User Interface by lloydde on Wednesday February 07, 2018 @11:08PM (#16330112)

Files don't overwrite each other the operation is forced. All of the OSs I've used will prompt you before overwriting.

I also like when an IDE detects and provides a warning when I have two variables with the same letters better different capitalization.

Different case is often a bug.

[ Parent | on HN ]

Re:Designing Windows 95’s User Interface by Retra on Thursday February 08, 2018 @07:16PM (#16336799)

Files definitely do overwrite each other without prompting in my terminal. And it is straight bullshit that MacOS doesn't care.

[ Parent | on HN ]