Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73624
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain eliw.com designates 69.195.222.200 as permitted sender)
Message-ID: <5342C09E.7000404@eliw.com>
Date: Mon, 07 Apr 2014 11:13:34 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <533C0713.9070106@eliw.com> <lhl14g$dhp$1@ger.gmane.org>
In-Reply-To: <lhl14g$dhp$1@ger.gmane.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="Dja6dKV85lPDMJKPCwpqmDMO1HtBNFkNI"
Subject: Re: [PHP-DEV] About PHP6 ...
From: eli@eliw.com (Eli)

--Dja6dKV85lPDMJKPCwpqmDMO1HtBNFkNI
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/3/14, 9:16 PM, Good Guy wrote:
> Frankly it is daft idea to outsmart authors of PHP books just because
> they decided to write about PHP6.  We need them as much as they need
> us and it helps no one to out-maneuver them just for the sake of it.
>
> The numbering system should continue as it is so that we don't
> alienate users of PHP.  Why do you guys want to confuse them bu
> inventing yet another system?
>
> Simplicity is the key to success of a product and it should be carried
> on.  The only time we should jump one number is when #13 is reached.=20
> Apart from that the numbering system should remain as it is.

Hey Good Guy - A quick response to your points.

1. Outsmarting Authors

    First of all you do realize that 99% of the these situations, the
authors didn't pick those PHP6 titles right?  The publishers did.  The
authors that I have talked to wish that the publishers would please drop
those books.  The authors don't WANT their name associated with the
incorrect books, but they have no rights due to the contracts.
    And the publishers who are happy to keep the books for sale and in
print, right now, are going to be even more happy when we release PHP6,
and suddenly their book gets a huge spike in sales.
    We won't be hurting any authors if we rename it, and in fact, by NOT
renaming it we will be helping the publishers, who are perpetuating this
very long standing issue.  This isn't a case of 'someone jumped the gun
1 month ago'.  This is a very long standing and unique situation due to
the circumstances that surround the now dead PHP6 branch.

2. "Inventing another system"

    Honestly we aren't going to alienate users of PHP by 'skipping 6'
and calling it 7.  It's not inventing another system, it's just skipping
a number.  Besides the fact that this has happened very frequently over
the last 20 some years in software, even mainstream software with far
less savvy customers, and it didn't manage to skuttle products... As
Zeev pointed out, it's simply an FAQ question, and answered.   And as
Lester pointed out, it's not even changing the system at all.  Because
we did have a PHP6, it turned out to be a dead product branch.  So to
remove confusion the 'dead' PHP6 lives on in the release notes with an
explanation, and the next version released is 7

3. #13
  =20
    This final argument highly confuses me.  So you are arguing that
skipping 6 and going to 7 -- is a horrible idea and is going to confuse
all of our users.  Even though there are many legitimate reasons for
doing so.  Yet skipping 13 and going to 14, for purely superstitious
reasons, is encouraged?  That makes no sense.  If you feel that it's OK
to skip 13 and go to 14.  Then you should have no argument against going
from 6 to 7.

Eli


--=20
|   Eli White   |   http://eliw.com/   |   Twitter: EliW   |



--Dja6dKV85lPDMJKPCwpqmDMO1HtBNFkNI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNCwKIACgkQUTBVzmoxCKIiKACgu2+hldp5bFvOQfY2e3zgVQLb
aWMAn2F3XU6GgoyX30gzRv9rzruTcFIN
=nH7D
-----END PGP SIGNATURE-----

--Dja6dKV85lPDMJKPCwpqmDMO1HtBNFkNI--