>>Well, ummm... I like C# a lot and use it a fair amount, but I don't like the fact that it enforces case sensitivity in code. Given the many strengths of C#, I wouldn't want to pick another language just because it doesn't enforce case sensitivity, so I need to live with the "case sensitivity business rule" that C# imposes on me, whether I like it or not. It's not unlike the old silly shout "America, love it or leave it!" There is much to like and much to dislike, but I wouldn't want to bail just because of the things I dislike here. I have to learn to live with the things that don't appeal to me, and enjoy the things that do.
>>
>
>But isn't this the case with just about everything? You like some things, dislike others. In many cases you don't get a choice to change only some aspects of something you like. So you decide if, on whole, you like it more than the alternative. And if the choice was added you may disrupt the reason other people liked it - for the lack of the choice.

Yes it is. But, again, the point here to me at least is "choice." IMO case sensitivity is an unnecessary restriction imposed by the development environment. Some people see it differently, but I for one don't see any compelling reason for a case sensitive language, because it adds another layer of potential silly mistakes on top of your regular everyday typos.

I suspect that case sensitivity is a legacy leftover from the time when compiler designers had to squeeze every last bit of performance out of the strictly limited CPU resources, and one way to streamline things was to not try to use CPU cycles to translate "MyVariable" to "myvariable", for example. Today the price of a CPU cycle is virtually zero, so letting the compiler and the CPU determine the "meaning" of a word regardless of its "casing" is the prudent thing to do. You couldn't do the same with typos, of course, but intellisense will take care of those just like a spell checker does for a word processor -- although you as the participating human in that process still have to make the final decision from a list of possible choices. Not necessarily so with casing in code. And I'm speaking strictly about coding, data is a different story, of course.