>Programs must be written for people to read, and only incidentally for machines to execute

True. But programs should also be forgiving when it comes to casing. People do make mistakes and computers should be able to detect and automatically adjust to the simple and obvious ones, like "wrong case but the right word." IOW, if I accidentally reference "MyNewVariable" as "MyNewvariable", the computer shouldn't worry about it. Beyond improving legibility (and I'm all for it), casing shouldn't matter to the computer in the least.

In the case of C (or C#), for example, the language would become completely backward INcompatible if case sensitivity was removed. Jets would fall of the sky, banks would go crazy, vehicles would stall unexplainably, etc., so there's a very good reason for keeping it in legacy languages that imposed this restriction long time ago for, I assume, faster processing considerations. But any new language should not have this restriciton, IMO, and maybe even legacy languages should have a case sensitivity compiler switch that people could turn off for brand new projects.

>
>>The thing is, our brains will pause to process words that have strange mixed casing, such as siLIcoN vAllEy, in order to translate it to the more familiar Silicon Valley, but w will eventually manage to translate the word regardless of casing. So proper casing is important with the written word. Computers, on the other hand, tend to have a lot of extra CPU cycles to process and translate whatever is thrown at them, as long as spacing is done right (e.g., Silicon Valley vs. sILIconvAlLEY), so why not make it easy (as in VFP versus C#)