Re: PHP 5.6 life cycle

Den 2015-12-08 kl. 16:00, skrev Adam Howard:

The EOL (end of life) date does influence people. True, not everyone will simply jump ship upon EOL. But it is still has a significant enough influence on adoption and urgency in general. Especially toward new development projects or new releases in general that are less likely to code with support for EOL products (overall). There is an influencing factor that cannot be realistically denied without avoiding common sense. On Tue, Dec 8, 2015 at 7:19 AM, Johannes Schlüter <johannes@schlueters.de> wrote:

On Sun, 2015-12-06 at 15:17 -0800, Stanislav Malyshev wrote:

Sufficient for what? It is a hard fact that people still run 5.3 version. In fact, 2/3 of sites run EOLed versions. You can always say they have only themselves to blame, but then I'm not sure what "sufficient" means. Unless adoption patterns change drastically, by the end of 2017 most people will not be running PHP 7. That's not something we can realistically change (unless you have some way of changing those patterns we didn't try yet or they change by themselves somehow). Thus, our choice lies only in whether we support this majority of users in some way or say "you are on your own now, we don't care about you

anymore". People who don't update aren't really relevant for a lifetime discussion. It doesn't really matter if they don't update to 5.6 or if they don't update to 7.0. Especially if they don't even update from 5.3.x to 5.3.(x+n). johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php Actually our ISP is now offering PHP 7.0 in their production environment for all

customers. So the 5.6 support timeline was not relevant in that case. For us as application developers I'm not sure it matters so much since we today runs on an older PHP version. The business case going for 7.0 is so good that I see no point going for 5.6 and then 7.0. Regards //Björn PS Of course for a larger organisation then us it has another impact, but the tentative cost savings and performance gains with 7.0 is a strong driving force.