Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82080
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <031501d04217$b393bff0$1abb3fd0$@tekwire.net>
References: <CA+9eiLuNjTa8JzBgnZE5iuv5BZ4Kw4Ehk1ivxPUetNSmZ43JMw@mail.gmail.com>
	<54D37D41.2030706@hoa-project.net>
	<CAGa2bXa_E27ZK89j-C3c0-Kj8pDY4EN_8U6SQC2K19SNm46wqg@mail.gmail.com>
	<54D470FA.6000303@hoa-project.net>
	<CAGa2bXaGE3QWjGxvRadLG0btA5wd1u5bZ=AAo6WQHE_Uek8iaw@mail.gmail.com>
	<02d301d041f3$0c5f3990$251dacb0$@tekwire.net>
	<CAGa2bXafsdmTPutaYP_oyX9CbjaRcJyqk0r3_v-ud=yCiQT_SA@mail.gmail.com>
	<CAGa2bXZnBWoL7NogbQCrfy-80G7xWoD_EJT3KH3v9aPiJ68Csw@mail.gmail.com>
	<031501d04217$b393bff0$1abb3fd0$@tekwire.net>
Date: Sat, 7 Feb 2015 10:48:07 +0700
Message-ID: <CAEZPtU7qg4U-ybQQc9NjapLu-uh0Q--FjmVAtnxEtc3_+LrOJQ@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>
Cc: Yasuo Ohgaki <yohgaki@ohgaki.net>, Dmitry Stogov <dmitry@zend.com>, 
	"Ivan Enderlin @ Hoa" <ivan.enderlin@hoa-project.net>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Design by Contract
From: pierre.php@gmail.com (Pierre Joye)

On Fri, Feb 6, 2015 at 9:17 PM, Fran=C3=A7ois Laupretre <francois@tekwire.n=
et> wrote:
>> De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo Oh=
gaki
>
>> Personally, backward compatibility is not too important.
>> PHP5 is dead by PHP 7.2 release... This is the reason why.
>> It's only 3 years later, only 2 years later after PHP 7.0 release.
>
> That's where we disagree, as I think it's most important.
>
> Thinking that PHP 5 is dead in 3 years is extremely na=C3=AFve IMO. You p=
robably didn't live the PHP 4/5 migration but I guess we won't have more th=
an 30 % of production servers under PHP 7 in 2018, just due to the delays o=
f distros, hosting companies, and others.
>
> Now, suppose you're distributing a library or a framework, like Symfony, =
Doctrine, etc. Someone tells you : "Here's the new DbC feature. You can use=
 it but this implies splitting your code to two independent branches and ma=
intain them in parallel until you have no PHP 5 customer anymore.". What do=
 you think you'll do (or won't do) ?
>
> @Pierre,@Dmitry : you have a better vision than mine on the migration pro=
cess. What's your opinion on forcing software developers to maintain two se=
parate branches ?

From a SemVer point of view, two branches are the worst thing we could
do. The same  applies to extensions btw.

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org