>>>>>Re: "However, having tried out the full LAMP stack..." -- now, if they could only do away with case-sensitivity. A real bane!
>>>>
>>>>Nah - you just have to change gears. Lots of languages, like C#, are case-sensitive, even on Windows.
>>>
>>>Oh, yeah, I know. But case-sensitivity is perhaps the most stupid thing ever put into a programming language.
>>
>>What's the big deal? The compiler will let you know if you get the case wrong. It's only a problem in loosely typed languages like xBase.
>
>See my response to Al. The bottom line is that it brings not benefits to the table. All it adds is potential problems.

Case in point: Unix -based webservers. When I email a link to my website, especially deeper in the hierarchy, I ALWAYS have to worry about case sensitivity and test it carefully before clicking SEND on my email client. More often than not, I have capitalized something that I shouldn't have capitalized, or vice versa. It is absolutely infuriating.

When you think about how our brains process text, it doesn't really matter how the casing is done in a given word -- our brains always translate it back to the actually meaning. "Bridge", "bridge", "bridgE", "bRIDGe" etc. gets translated to "bridge", although some forms of it (e.g., "bRIDGe") take a few more brain cycles to process. This is probably the reason why early compilers, such as C, had the case sensitivity rule -- it took a few extra CPU cycles to translate the meaning of the word if strict casing rules were not enforced. Today's CPUs are mostly sitting around, idling, starved for something, anything, to process, so the rule does not apply any longer.

Computers should work like our brains, not the other way around. I propose a LAW that BANS case sensitive programming FOREVER.