Re:Request for Java 8 support on Google App Engine
by randomfool on Tuesday June 09, 2015 @10:06AM
(#9685962)
https://code.google.com/p/googleappengine/issues/detail?id=9...
Sounds like their answer for Java8 is probably the same for Python3:
"To echo comment #66, App Engine in fact is not going away. To the contrary, we're investing heavily, and the new hosting environment that is based on containerized virtual machines (what we're currently calling "App Engine Managed VMs") allows you to utilize Java 8 as well as Servlet 3.x."
Re:Request for Java 8 support on Google App Engine
by nly on Tuesday June 09, 2015 @10:16AM
(#9686010)
Snapchat runs off the back of App Engine, I don't think they're going to ditch it anytime soon.
Re:Request for Java 8 support on Google App Engine
by chii on Tuesday June 09, 2015 @10:42AM
(#9686177)
why would snapchat's decisions have any consequence for google's appengine roadmap?
Re:Request for Java 8 support on Google App Engine
by lmm on Tuesday June 09, 2015 @11:20AM
(#9686433)
Because Snapchat is a large enough client that Google cares about keeping them happy? (Not that I believe that)
Re:Request for Java 8 support on Google App Engine
by rahij on Tuesday June 09, 2015 @10:47AM
(#9686211)
IIRC, Snapchat moved off of app engine to EC2 last year.
They update the SDK quite regularly: https://code.google.com/p/googleappengine/wiki/SdkReleaseNot...
They rarely handle bugs well. The linked issue is typical. They don't even need to do any work to do a whole lot better; they just need to give developers an indication about what to expect. That does mean that they need to make decisions internally, which might be the problem. Potentially, management is umm'ing & arr'ing about whether to kill App Engine.
They recently threw a bit of a contribution in the direction of AppScale, but it's difficult to read that. It could be to soften the blow in the event of discontinuation, or it could be to remove the perception of App Engine as a service with no alternative.
There have also been new features recently introduced, albeit projects that seem like they should have lower prioritization than ensuring folk can use SSL with App Engine, or use modern versions of their programming language. For example, this recent addition: http://googlecloudplatform.blogspot.com.au/2015/02/using-goo...
My reading of the situation is that Google Cloud folk have resources (headcount) to do routine maintenance on App Engine, but not embark on any infrastructural advancements, like new versions of Python & Java, or significant new functionality.