>>>The point is that it has nothing in the "pro" list and lots in the "con" list. There is really no good reason for case-sensitivity. You're constantly doing something or using some tool in order to get it right. And not every case sensitive language has those tools. Take JavaScript for example. It trips you up. You're writing some complex code and get fooled by an error that actually turns out to be a case issue when you're looking past that to something more complex. Then you realize its a stupid case issue. We have enough troubles in this industry with the relentless change, integration of complex technologies, etc., etc. etc. We don't need to trip ourselves up with stupid issues like case-sensitivity.
>>
>>Case-sensitivity promotes rigour and attention to detail, which are thematic in programming.
>
>That's a hoot. In 20 years of programming, during which time I have followed up behind a number of programmers, I've never found myself - not even once - worrying about the case of variable names. This issue is so low on the priority list as to be nonexistent. The problems are usually things like a lack of understanding about data normalization, SQL, granularity, boolean logic, and on and on. Once I followed up behind someone that had written what was far and away the worst program I've ever seen. He smashed every rule in the book. It was astounding how bad it was. Not only bad, but there was some really weird "techniques" (if you could call them that) that he used. If you could invert that - make it a great programming example instead of a horrible one - but leave in case inconsistency in his variables, etc. then I wouldn't have a care in the world. I wouldn't criticize it even one billionth of a percent. Could someone make it painful. SuRE tHEY couLD If ThEy WANted To BUt YOU Won'T FinD thAT. It's mainly minor discrepencies.
>
>Another example: Case-sensitivity in Linux. They brought it over from the programming environment, mistakenly thinking what a great thing it is. You know what they have to do in order to get regular people using Linux. They have to remove it so that when you search for a file name, you don't have to have the case exactly right. Imagine some CEO or CIO looking for the some document related to the big presentation and he/she can't find it because when he typed it into the search field, he didn't use the same case. Do you think Linux would ever get into or stay in that corporation after that? No, he'd never let it in or toss it out and he'd find (or would like to find) the programmers that made that idiotic decision and rip their heads off and defecate down their necks. So the smarter programmers remove that issue from their search tools. And that is probably the best reason not to have it. If it's a problem that needs to be worked around, it's better to fix the root cause than treat the symptoms. Case-sensitivity should have never been invited to the party.

Personally I *much* prefer case sensitive languages. One neat feature in VS2010 which couldn't exist if C# wasn't case sensitive is the QuickFind for types which relies on camel casing. Searching for, for example, "MC" will bring up all types such as
MyCustomProperty, MyCustomClass, MyCustomMethod etc....