I never get this about google. They had a great product here (I and I know others actively interested) but they just drop development on these things for the new shiny toy. We're not asking for a ton, but if you could assign even a few folks to maintain the non-cool stuff, I think a lot more folks would build on GCP.<p>I'm on AWS currently. They keep their old / uncool stuff around in a nice way (and totally seem to drop ball on other stuff that matters less like their new Amazon Linux 2 effort - python 3 support in that is totally wonky etc).
For anyone confused, currently you have a choice of either "Standard Environment", which is Python 2.7 only, or "Flexible Environment" which allows you to choose Python 2.7, Python 3.6, or your own Python runtime [1][2]. This is about supporting Python 3 in the "Standard Environment". It's unclear whether the intention is to replace Python 2 or allow a choice?<p>[1] <a href="https://cloud.google.com/appengine/docs/python/" rel="nofollow">https://cloud.google.com/appengine/docs/python/</a>
[2] <a href="https://cloud.google.com/appengine/docs/flexible/python/runtime" rel="nofollow">https://cloud.google.com/appengine/docs/flexible/python/runt...</a>
I love the new movement in on GAE Standard. With GAE Flexible, GKE, Cloud SQL, etc there's actually a growth path for something that out grows it. When Standard first launched, that additional complexity meant a rewrite.<p>Can the Java runtime implement the full Servlet 3.1 spec now? It's 5 years old (and most Scala http libs don't support blocking Servlets anymore).
Just in case you're like me and had to Bing what the difference is between Docker and Google App Engine, it's summed up really well in this Stack Overflow answer:<p><a href="https://stackoverflow.com/a/49950687/3799" rel="nofollow">https://stackoverflow.com/a/49950687/3799</a><p>I wonder, though, if future development should target Docker/K8S and GAE should only be the domain of legacy applications.