I still think it's a terrible default, though. I'm coming to OSX from BSD and using it as a Unix. Retrofitting case-insensitivity onto a Unix is bound to lead to ugly corner cases.
It generally works well, but the other way around does not work: many OSX software (most prominently — as usual — adobe's) play fast and lose with casing, and will break down on case-sensitive HFS+.
On top of which, it would have been an added complication for developers porting from Classic, and an unexpected change for users, in exchange for no substantive benefit.
In truth, the only time HFS+'s case-insensitivity has bitten me was extracting an SDK from Broadcom, and even then, the SDK wasn't about to run on OS X anyway (it's entirely Linux-based), I was just pulling out some documentation.
Indeed, I've had to make password systems case-insensitive for similar reasons.
I definitely recommend against using case-sensitive HFS+. It's a pain to fix because you have to reformat, and you can't restore from a Time Machine backup because Time Machine requires that the source and target file systems are case-compatible. :-/
Yeha, I wouldn't blame a tool for not dealing with the brain-dead almost case-sensitive HFS+ filesystem.
I prefer case-sensitive filesystems because the separation between works is semantically meaningful in English.
I had a similar issue with Perforce on Windows - Perforce was case sensitive, Windows wasn't, and thanks to CamelCase, there were two files that had the same letters but different casing. (I don't remember the names.)
* Technically, "case-insensitive but case-preserving", which in practice seems to mean, "case-sensitive, except when you need it to be".