Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100575
Return-Path: <TonyMarston@hotmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 71052 invoked from network); 14 Sep 2017 09:21:03 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 14 Sep 2017 09:21:03 -0000
X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk  
Received: from [62.31.75.76] ([62.31.75.76:14229] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F1/A9-19300-DF94AB95 for <internals@lists.php.net>; Thu, 14 Sep 2017 05:21:02 -0400
Message-ID: <F1.A9.19300.DF94AB95@pb1.pair.com>
To: internals@lists.php.net
References: <c7746903-2e3a-3e86-59c9-63483b244feb@gmx.de> <CAESVnVpUkM_W9xF+0Qt=2M61dGy40gtOehFo=U_F3gd87rmxrQ@mail.gmail.com> <3D.0C.10715.383F8B95@pb1.pair.com> <CAESVnVp6OKB64WuO9iKEP=L9-QrrFjS+kcoeKYKULRUff-RitQ@mail.gmail.com>
In-Reply-To: <CAESVnVp6OKB64WuO9iKEP=L9-QrrFjS+kcoeKYKULRUff-RitQ@mail.gmail.com>
Date: Thu, 14 Sep 2017 10:20:57 +0100
Lines: 3
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216
X-Posted-By: 62.31.75.76
Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants?
From: TonyMarston@hotmail.com ("Tony Marston")

"Sara Golemon"  wrote in message 
news:CAESVnVp6OKB64WuO9iKEP=L9-QrrFjS+kcoeKYKULRUff-RitQ@mail.gmail.com...
>
>On Wed, Sep 13, 2017 at 8:59 AM, Tony Marston <TonyMarston@hotmail.com> 
>wrote:
<snip>
>> People who think that case sensitive software is cool are deluding
>> themselves. When I started working on mainframe computers (UNIVAC and 
>> IBM)
>> in the early 1970s everything was case-insensitive. This was only changed 
>> by
>> people who did not understand the ramifications of their choice.
>>
>Yeah, decades of C/C++/Java developers are so dumb, like... fer reals.
>Friggin' script kiddies, the lot of 'em.
>
>-Sara

If the first programming languages in the first computers were case 
insensitive, then that should be the standard. Those who introduced case 
sensitive languages at a later date should be forced to justify that 
decision. It is the same for file systems - all the pre-unix systems I 
worked on were case insensitive, as have been all versions of Microsoft 
Windows. Then unix came along and FUBAR'd everything. Any advantages of case 
sensitive systems are ALWAYS outweighed by their disadvantages.

A similar cockup occurred with line endings. The original convention on 
teletypes was to use line-feed (LF) and carriage-return (CR) together which 
have separate meanings and could either be used independently or together. 
Then some clueless newbies came along and changed everything so that some 
OSes use just LF while others use just just CR. This now causes problems 
when transferring files from one OS to another. This shows what happens when 
"friggin' script kiddies" (your words, not mine) come up with an idea 
without understanding what the current convention is.

-- 
Tony Marston