为什么Google App Engine Standard使用PHP 5.5? [英] Why is Google App Engine Standard using PHP 5.5?

问题描述

我计划在Google App Engine标准中托管PHP应用程序，但我发现一件非常令人担忧的事情:

I plan on hosting PHP applications in Google App Engine Standard, but i find one thing quite concerning:

当前，您可以在PHP 5.5运行时和beta 7.2运行时之间进行选择.因此，当前可用的非Beta版本是5.5，它的寿命是1 1/2年前！

Currently one can choose between a PHP 5.5 runtime, and a beta 7.2 runtime. So the currently available non-beta version is 5.5, which had it's End-of-Life 1 1/2 years ago!

为什么很久以前未将其升级到5.6?为什么没有7.0或7.1环境(7.0是2年前问世的！)?提供这么老的PHP运行时不是完全不负责任吗?我的意思是，即使是最业余的共享托管公司，很久以前也可能已升级到5.6.我不明白，为什么Google-地球上领先的科技公司之一-会这样做.

Why was this not upgraded to 5.6 long ago? why are there no 7.0 or 7.1 environments (7.0 came out 2 years ago!)? Isn't it completely irresponsible to provide such an old PHP runtime? I mean even the most amateurish shared hosting companies probably have upgraded to 5.6 long ago. I can't understand, why Google - one of the leading Tech-companies on the planet - is doing this.

我知道我可以在灵活的App引擎中使用我想要的任何运行时，但是如果Google将标准PHP环境"解释为PHP 5.5，这对任何开发人员来说不是一个危险的信号吗?为什么现在有人不负责任地使用PHP 5.5或选择一个托管提供商，而后者却落后了，它提供了5.5作为最新的稳定PHP环境?这样的运行时如此保守和看似不负责任的升级模式不是一个大信号，不要对任何负责任的开发人员使用App Engine Standard?

I know that i can use any runtime i want in the flexible App-engine, but if "Standard PHP environment" is interpreted as PHP 5.5 by Google, isn't this a giant red flag for any developer? Why would anyone be so irresponsible to use PHP 5.5 nowadays or choose a hosting provider, that is THAT far behind, that it provides 5.5 as the most current stable PHP environment? Isn't such an incredibly conservative and seemingly irresponsible upgrade-schema of runtimes a big red flag NOT to use App Engine Standard for any responsible dev?

还是我在这里完全错过了什么?

Or am i completely missing something here?

推荐答案

在第一代标准环境沙箱中，许多服务都依赖于特制的库，API和支持的基础结构/服务.

In the first generation standard environment sandbox a lot of the services relied on specially crafted libraries, APIs and supporting infrastructure/services.

在更改支持的语言版本时，GAE团队很可能需要重写/移植所有/所有这些语言，并以及时且经济高效的方式进行，同时保持SLA并非易事.

Most likely many/all of these would need to be re-written/ported by the GAE team when changing the supported language version and doing so in a timely and cost-effective manner while maintaining the SLAs is not at all trivial.

您可以在从标准迁移服务中看到这些服务的列表.适应灵活环境的环境指南-即使不是全部，大多数也不能在第二代标准环境中使用.

You can see a list of these services in the Migrating Services from the Standard Environment to the Flexible Environment guide - most if not all of them aren't available in the 2nd generation standard environment either.

通过用其他Google(甚至第3方)团队提供的或多或少类似的解决方案来替换这些服务(或完全放弃它们)，添加对不同语言/版本的支持变得容易得多-可能解释了不断增长的速度这些内容栩栩如生并得到了发展-请参见带注释的历史Google的Cloud Platform 和/或 PHP发行说明.如果您愿意的话，这就是Google一直在积极努力跟上语言发展的证明.

By replacing these services with more or less similar solutions offered by other Google (or even 3rd party) teams (or dropping them altogether) adding support for different languages/versions became a lot easier - probably explaining the constantly increasing rate at which these came to life and evolved - see An Annotated History of Google’s Cloud Platform and/or the PHP Release Notes. Which is, if you want, proof that Google kept actively trying to keep up with language evolution.

我不确定PHP或其他语言，但对于我的应用程序使用上下文，我对较旧的python 2.7版本感到非常满意，尤其是考虑到第一代标准环境独有的其他优势时.我只是希望有了替代产品，维持它的成本(即使是冻结的状态)仍然足够低，以至于不能证明停产是合理的；)

I'm not sure about PHP or the other languages, but for my app usage context I'm more than happy with the older python 2.7 version, especially when taking into account the other advantages exclusively offered by the 1st generation standard environment. I just hope that with the alternate offerings in place the cost of maintaining it (even frozen as-is) remains low enough to not justify discontinuation ;)

这篇关于为什么Google App Engine Standard使用PHP 5.5?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！