On 4/2/14, 1:57 PM, Nikita Popov wrote:
> On Wed, Apr 2, 2014 at 2:48 PM, Eli <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hello everyone. I've been hitting a lot of conferences recently, and
> found myself having the same discussion with multiple members of the
> community. And many of them have 'heavily encouraged me' to bring
> this
> discussion up here. And Julien's recent PHP6 email, reminded me
> that I
> hadn't done so.
>
> The short form is:
>
> We should not name the next version of PHP: PHP6, for 2 reasons:
> 1. It will cause confusion in those least able to adapt
> 2. It costs us nothing, hurts us in no way, to name it
> something else
>
>
> There is potential for confusion regardless of what we do. If it's PHP
> 6, we get conflicts with existing literature. If it's PHP 7, this will
> lead to confusion about a version number being skipped. (Which is imho
> a pretty big wtf moment.)
>
> I find it quite ridiculous to break our versioning scheme over this
> kind of nonesense.
Nikita, thank you for your feedback. I would like to point out a major
difference between these levels of confusion here:
1. We name it PHP6, people who try to find information on PHP6, find old
books and old articles, read them, think they are accurate, learn
incorrect/wrong information, and get extremely frustrated when nothing
they are trying to do works. They will be taught bad information.
Things will not work. Worst case, they give up on PHP completely
because of it.
2. We name it PHP7, A majority of the 'non-connected' just see the
latest version and upgrade. The majority of the connected, understand.
Then there are some people go: "huh? what happened to PHP6", so they
google, and will find the story. At no point does anyone who is
attempting to learn, get taught incorrect material.
I would much rather have a few people go 'huh? What happened to 6'.
.. Then have people paying money for books, supporting authors who
'jumped the gun', for ancient information that is incorrect.
Thanks,
Eli
--
| Eli White | http://eliw.com/ | Twitter: EliW |
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc