Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99400
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender)
Date: Tue, 06 Jun 2017 13:57:10 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <10.6B.27119.02566395@pb1.pair.com>
References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> <CA+kxMuRoMvy6vB0YKd6Ejqu8AsKxrO2x6F9y5i9+cxfJSJ-ihg@mail.gmail.com> <A4.5C.12681.20F62395@pb1.pair.com> <op.y09fz0b4twp9n2@charlie> <F9.E2.12681.8AEC3395@pb1.pair.com> <3cfc0130-e530-64ed-36e8-372b044811a8@rhsoft.net> <03.F6.12681.AF215395@pb1.pair.com> <3351770B-C53E-4062-A91A-D3AA7439F02B@gmail.com> <10.6B.27119.02566395@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Tony Marston <TonyMarston@hotmail.com>
Message-ID: <661DCFAE-C27B-49D6-80CD-5E69579B0897@gmail.com>
Subject: Re: [PHP-DEV] Class Naming in Core
From: rowan.collins@gmail.com (Rowan Collins)

On 6 June 2017 09:17:31 BST, Tony Marston <TonyMarston@hotmail=2Ecom> wrote=
:
>"Rowan Collins"  wrote in message=20
>news:3351770B-C53E-4062-A91A-D3AA7439F02B@gmail=2Ecom=2E=2E=2E
>>
>>On 5 June 2017 09:14:47 BST, Tony Marston <TonyMarston@hotmail=2Ecom>
>wrote:
>>>Seriously, can you explain in words of one syllable the precise
>>>benefits of
>>>such a consistency?
>>
>>I will try:
>>
>>- When we write code, we need to know how to spell the names of
>things=2E If=20
>>the things all have names that look the same, it is less hard for us
>to=20
>>guess what the name is=2E This means we take less time to learn the
>names,=20
>>and get less things wrong=2E
>
>Words and abbreviations are spelled the same whether you use snake_case
>or=20
>CamelCase, the only difference is how you show the boundary between one
>word=20
>and the next=2E Studies have shown that snake_case is more readable than=
=20
>CamelCase=2E
>
>>- Our brains are made to spot when things are the same, and when
>things are=20
>>not the same=2E When one thing is not like the things near it, we think
>"why=20
>>is that?" This slows us down=2E
>
>Seeing a name written in snake_case does not slow you down=2E In normal=
=20
>writing there is a space between each word, but as names in software
>cannot=20
>have embedded spaces=2E This is why underscores are used, and this is=20
>infinitely more readable than replacing spaces with a capital letter=2E
>
>>- When we get things wrong, we need to find out what we did wrong=2E If
>one=20
>>way to write a name is wrong, we can spot when we wrote it that way,
>and=20
>>know that it is wrong=2E
>
>Writing a name wrong has nothing to do with the difference between=20
>snake_case and CamelCase=2E My IDE will show me existing names that match
>what=20
>I am typing as soon as I start typing, so I can easily pick the name
>that I=20
>want=2E
>
>>- If we make two things that mean the same thing, but do not look the
>same,=20
>>we might not spot that we wrote a third thing that does not mean the
>same=20
>>thing=2E
>
>If you try to instantiate a class that does not exist, or call a=20
>method/function which does not exist, then you will soon know about it=2E
>
>Using snake_case instead of CamelCase does not invite more errors=2E
>
>>I think there are more things that make it good to have names that
>look the=20
>>same, but I hope this helps for now=2E
>
>The only universally accepted "rule" for names is that they be unique
>and=20
>convey proper meaning=2E In proper languages all names are
>case-insensitive as=20
>the ability to write the same name with the exact same spelling but=20
>different case is simply inviting disaster=2E


Hi Tony,

I think it's clear at this point that we're never going to agree here=2E W=
e don't seem to even agree what the topic of discussion is - consistency in=
 general? CamelCase in general? Richard's RFC? the authority to choose thin=
gs? etc

More importantly, we're not going to change the minds of the people who wi=
ll actually make this decision by filling the list up with our debates=2E W=
e're just wasting our own time and everyone else's, so I'm going to stop he=
re=2E

Regards,

--=20
Rowan Collins
[IMSoP]