🚀 go-pugleaf

Sorry, but that's just a bunch of crap, and some of of it may have been true 2 years ago.

First, the standard Mac OS X 10.5 (Leopard) which has been out for ~1.5 years has the case sensitive option available to all users on, not just server, via the standard installer. Clearly this shows that Apple has said it's OK to use the case sensitive file system.

Second, both my home and work Macs have been running the case sensitive file system for well over a year and I have 104 applications installed on my Mac at home and 57 on my Mac at work and EVERY single app works fine on the case sensitive file system EXCPET Adobe Reader. That's my only Adobe product. Doesn't that tell you something?

Third, a case sensitive file system is what we should all be using, that's what we use in real language, and we should not still be restricting ourselves to design decisions of the 1980s where memory and disk space was so expensive that it was saved by using case insensitive filesystems. It's just not right that the file named "you must read me" is the same as the file "You MUST READ me".

Lastly, do you know how easy it is to write software that works with a case sensitive file system? Actually it requires ZERO extra effort. There is no support. All you need to do is actually TEST your software properly. Think about it. If software doesn't work with a case sensitive file system it is because the software is looking for a file with a different case name the the file actually exists on the disk. For example, the software looks for "MyPreferncesFile" and on the disk the it is "mypreferencesfile". This is a programming mistake!

So, really there is nothing to do to support a case sensitive file system other than properly developing your software. So, I can rephrase my question if you like and ask for the software to be properly written and debugged instead.

I know that Adobe is always way behind, but this is ridiculous.