OS X is case-insensitive in the FS by default, so I guess that's a win? You'll never notice it until one day you lose a file when you're unpacking an archive f

OS X is case-insensitive in the FS by default, so I guess that's a win? You'll never notice it until one day you lose a file when you're unpacking an archive from another platform that has different files named Makefile, makefile, and MAKEFILE (not that I'm condoning that practice). More importantly, case folding is complicated or ill-defined in some non-English languages, and there are presumably edge cases in the algorithms. So it gets harder to tell what any given code will do. If "var x" and "VAR X" were the same in JavaScript, we'd just have to make our company style guide longer. Having more ways to write different-looking but equivalent code isn't necessarily a good thing. Sure, it's fun to write code like this: Circle circle = Circle.CIRCLE; But were I to use a case-insensitive language, I'm pretty sure I'd get comfortable not being able to do so. Sounds like the kind of thing you should try before advocating it.