Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!news.alt.net!not-for-mail From: owl Newsgroups: comp.os.linux.advocacy Subject: Re: Snit, when you say cola trusts your views on 'pretty much any topic'... Date: Thu, 26 Mar 2015 21:34:09 +0000 (UTC) Organization: ok by me, so long as it doesn't get out of hand Lines: 61 Message-ID: References: <14a7f4dd-6a56-4276-8901-d67234f8f240@googlegroups.com> NNTP-Posting-Host: boom.rooftop.invalid User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.6.38-16-generic (x86_64)) Xref: csiph.com comp.os.linux.advocacy:286302 GreyCloud wrote: > owl wrote: >> DFS wrote: >>> On 3/26/2015 10:48 AM, Steve Carroll wrote: >> >>>> I appreciate the additional space that case sensitivity provides for >>>> identifiers. >> >>> Fact is, it's incredibly ridiculous to allow two variables (or words, or >>> file names, or folder names) to be spelled the same but mean something >>> different or store something different because of the case of one letter. >> >>> recSet >>> RecSet >>> completely different cursor variables! >> >> RekSet >> >>> SLE-12-Desktop-DVD-x86_64-GM-DVD1.iso >>> SLE-12-desktop-DVD-x86_64-GM-DVD1.iso >>> completely different files! >> >> SLE-Twelve-Desktop-DVD-x86_64-GM-DVD1.iso >> >>> trash >>> Trash >>> Completely different folders! >> >> Why not? They have different names. >> >> owl@thinkpad:~$ echo "trash" | hexdump >> 0000000 7274 7361 0a68 >> 0000006 >> owl@thinkpad:~$ echo "Trash" | hexdump >> 0000000 7254 7361 0a68 >> 0000006 >> owl@thinkpad:~$ >> >> >>> Case-insensitive and case-preserving is the best (like Windows and VB >>> does it). >> >> No, that's retarded. > Erm, VMS was that way as well. Probably why NT is so retarded. > It actually worked out for the better in an > environment that just used terminals. > OS X default is that way too. Need I say "retarded"? > Sun Solaris isn't, but the long file names > were a bitch under the usual SH (sh) shell. It didn't have command line > history. What they needed was a "~"