Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123610
Precedence: bulk
MIME-Version: 1.0
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> <33b28a8d-7d30-497b-b457-728f21188417@scriptfusion.com>
In-Reply-To: <33b28a8d-7d30-497b-b457-728f21188417@scriptfusion.com>
Date: Fri, 14 Jun 2024 23:59:31 +0300
Message-ID: <CAPyeZ4OXj_2E4qVAQzECFU1BaxjRO7EYu8ffuZHa6PKPh2i2rQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Revisiting case-sensitivity in PHP
To: Bilge <bilge@scriptfusion.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000015861c061adfe550"
From: udaltsov.valentin@gmail.com (Valentin Udaltsov)

--00000000000015861c061adfe550
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Friday, 14 June, 2024=E2=80=AFat 23:19, Bilge <bilge@scriptfusion.com> w=
rote:

> 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 perfor=
mance 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 mana=
ge edge cases is not worth the hassle.
>
> At the moment, I'm leaning No on this change, because the cost/reward/bac=
klash 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
>
> Yes, I am working on this.
--=20
Valentin Udaltsov

--00000000000015861c061adfe550
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Friday, 14 June, 2024=E2=80=AFat 23:19=
, Bilge &lt;<a href=3D"mailto:bilge@scriptfusion.com">bilge@scriptfusion.co=
m</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><u></u>

 =20
   =20
 =20
  <div>
    <div>On 14/06/2024 15:56, Larry Garfield
      wrote:<br>
    </div>
    <blockquote type=3D"cite"><span style=3D"white-space:pre-wrap">
</span><span style=3D"white-space:pre-wrap">
</span>
      <pre>I agree that this sounds like a change with very unclear BC impl=
ications at best, and bad ones at worst, with dubious benefit.  Just how mu=
ch performance would we gain from case sensitive class names?  If it&#39;s =
20%, OK, sure, that may be worth whatever BC breaks that causes on the marg=
ins.  If it&#39;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&#39;m leaning No on this change, because the cost/reward/b=
acklash ratio is just not there to support it.

--Larry Garfield
</pre>
    </blockquote>
    <div dir=3D"auto">Would be good to see some real-world metrics,
      whether or not they&#39;re the principal/only reason this might be a
      good change.<br>
    </div>
    <div dir=3D"auto"><br>
    </div>
    <div dir=3D"auto">Bilge</div>
    <p></p>
  </div>

</blockquote></div>Yes, I am working on this.<br><span class=3D"gmail_signa=
ture_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div =
dir=3D"ltr">Valentin Udaltsov<br></div></div></div>

--00000000000015861c061adfe550--