Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65677
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
Sender: thbley@gmail.com
In-Reply-To: <51113192.2030404@lsces.co.uk>
References: <CAOfzkkz3DC+aVb4c73QHGRzZv=1z=nG4uexdJh2n8h3ATGBBOA@mail.gmail.com>
	<CAEZPtU6UdX4uyR7tLomi==DNbmJduHoxa=qmb+dd2bJQKcoxjw@mail.gmail.com>
	<CAOfzkkwQNKRrX+MQ3JutkVWmHsCLZetJMp7AubA52E+=MSCcXw@mail.gmail.com>
	<510EBF98.4060900@lerdorf.com>
	<CAOfzkkwU4=K86582q1kgh_w2Ecubxij-ExecBLF_aHEWMY=dew@mail.gmail.com>
	<CAKOpQSyuKoSY8JGNhYUxPNTECR30Kk8j8MY5r4tY0qS_xBju2A@mail.gmail.com>
	<CAOfzkkwLODYXEyzEb1uNp6+ANUSZ9w80p3L7S5YoT6iGA1zRhA@mail.gmail.com>
	<5110AFFB.8040303@lerdorf.com>
	<5110BF7F.90508@lsces.co.uk>
	<1360065708.95691.YahooMailNeo@web133004.mail.ir2.yahoo.com>
	<5110FE4B.8020406@lsces.co.uk>
	<CAEZPtU6yNikOhrO3s_R8dx-WMVJ-nxLcKvB9AmMFyB=6+BdS5Q@mail.gmail.com>
	<51113192.2030404@lsces.co.uk>
Date: Tue, 5 Feb 2013 17:37:24 +0100
Message-ID: <CA+_UWzqfo+cU8bn1gH5fCzb6OBHpb2KsqRYnpsEeugQ2XBVe8w@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Proposal for serious BC compatibility aka language versioning
From: thbley+php@gmail.com (Thomas Bley)

On Tue, Feb 5, 2013 at 5:21 PM, Lester Caine <lester@lsces.co.uk> wrote:
> Pierre Joye wrote:
>>
>> If you do commercial support for customers and do not control the
>> environment and/or use shared hosting, then something is totally wrong
>> in your business model. It is also really off topic, in this mailing
>> list or in this discussion.
>
>
> It is totally on topic!
>
> The REASON I have gained this particular additional customer base is because
> they are all having problems with keeping their sites active! I had hoped to
> be producing a better set of documentation to help these type of users to
> cope with the 'BC compatibility' problems they are currently fighting, but
> there is nothing consistent to document. There are as many problems as
> customers with several years of legacy code written by different programmers
> :( THEY are not programmers ...
>
> I hope that as some point there will be some REAL support for stopping
> 'developing' PHP5 and move all of the new 'features' being discussed into a
> nice cleanly isolated PHP6 development stream. Then we can start documenting
> what IS being removed and stop trying to track which legacy feature needs to
> be re-worked rather than simply burying heads in sand and hiding them!!!
>
> My current roadmap is based on PHP5.4 servers with nothing hidden and
> eventually all of the code will be moved forward to that base, but I simply
> can't justify charging some customers for all the time this takes because
> they HAVE working sites currently and this is not giving them any return.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

> I hope that as some point there will be some REAL support for stopping
> 'developing' PHP5 and move all of the new 'features' being discussed into a
> nice cleanly isolated PHP6 development stream.

Just see it as a car: you can drive it 10 years or longer, but from
time to time you need new tires or repair some stuff.

Regards,
Thomas