Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123606
Content-Type: multipart/alternative;
 boundary="------------R3T2pLru1O4LdrBH5M2ri8vN"
Message-ID: <33b28a8d-7d30-497b-b457-728f21188417@scriptfusion.com>
Date: Fri, 14 Jun 2024 21:15:17 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Revisiting case-sensitivity in PHP
To: internals@lists.php.net
References: <CAPyeZ4O2rK+2ApuE-YLc7j_Z2LcT29yHcLYXvB0oGs-D_zTSag@mail.gmail.com>
 <CAMjSS5OPKm0dRP+ckCdpBd4Kg1aRhU5QgcuTWwPTnyC_1aZRkw@mail.gmail.com>
 <CAPyeZ4PCGuosZMrj9jvwXQnBuSdoqXsVFEEArUDpOkxTMk_h+Q@mail.gmail.com>
 <CAF-mU4yqj_sWPFJPmAsP6gHKguWVa5NfXto2qAvfdMm0G342CQ@mail.gmail.com>
 <CAPzBOBM-bULK-3S1aFzDgf5qcpw_jn9_N2KHAJB1sWm3gCVSWA@mail.gmail.com>
 <923a3373-1963-4239-b218-bcdada899024@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <923a3373-1963-4239-b218-bcdada899024@app.fastmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------R3T2pLru1O4LdrBH5M2ri8vN
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 14/06/2024 15:56, Larry Garfield wrote:
> I agree that this sounds like a change with very unclear BC implications at best, and bad ones at worst, with dubious benefit.  Just how much performance would we gain from case sensitive class names?  If it's 20%, OK, sure, that may be worth whatever BC breaks that causes on the margins.  If it's 0.2%, then frankly, no, the PR cost of pissing off people who have to manage edge cases is not worth the hassle.
>
> At the moment, I'm leaning No on this change, because the cost/reward/backlash ratio is just not there to support it.
>
> --Larry Garfield
Would be good to see some real-world metrics, whether or not they're the 
principal/only reason this might be a good change.

Bilge

--------------R3T2pLru1O4LdrBH5M2ri8vN
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 14/06/2024 15:56, Larry Garfield
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:923a3373-1963-4239-b218-bcdada899024@app.fastmail.com"><span
      style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span>
      <pre class="moz-quote-pre" wrap="">I agree that this sounds like a change with very unclear BC implications at best, and bad ones at worst, with dubious benefit.  Just how much performance would we gain from case sensitive class names?  If it's 20%, OK, sure, that may be worth whatever BC breaks that causes on the margins.  If it's 0.2%, then frankly, no, the PR cost of pissing off people who have to manage edge cases is not worth the hassle.

At the moment, I'm leaning No on this change, because the cost/reward/backlash ratio is just not there to support it.

--Larry Garfield
</pre>
    </blockquote>
    <div dir="auto">Would be good to see some real-world metrics,
      whether or not they're the principal/only reason this might be a
      good change.<br>
    </div>
    <div dir="auto"><br>
    </div>
    <div dir="auto">Bilge</div>
    <p></p>
  </body>
</html>

--------------R3T2pLru1O4LdrBH5M2ri8vN--