As far as I assumed, and I'm too optimistic these days, they'll work
indefinitely?
https://cloud.google.com/appengine/docs/standard/long-term-support
I'm probably never going to move my old apps to 3.7, they'll die when 2.7
dies - they use pretty much every available original in-house app
> On Apr 19, 2020, at 1:01 AM, MdeA wrote:
>
> Now I'm just wondering what will happen to all my web apps running on GAE
> after July, 2020.
Short answer: They will continue to work as they have been.
We need to migrate from Py2.7 to Py3.7 and the new stack, but google is giving
us years
Hi! You can find the official statements regarding Python2 in this
documentation pages [1][2].
[1]: https://cloud.google.com/python/docs/python2-sunset
[2]: https://cloud.google.com/appengine/docs/standard/long-term-support
On Tuesday, March 24, 2020 at 3:02:55 PM UTC+1, bFlood wrote:
>
> Is
Is there an official AppEngine Standard Python 2.7 depreciation date? the
SDK (appcfg) is gone in July2020 but has anything been announced with
regard to the runtime/hosting environment yet?
thanks.
On Monday, March 23, 2020 at 11:54:50 AM UTC-4, Olu wrote:
>
> Thank you for your feedback,
Thank you for your feedback, Alexey and I understand your concerns. I
however encourage you to use the issue tracker links for creation of
features[1] that you consider would be nice to have on GCP. The team are
committed to reviewing such requests and considering how these requests fit
into
I feel like Google has made some improvements and some of the deprecations
are understandable. My biggest issue is the way Google has gone about
doing this. GAE started out as a platform coded to a number of languages'
interfaces, some standard and some proprietary. For example, it used to
As another longtime user, I have mixed feelings. Some things are better,
some things are worse. I certainly wouldn't give up the current GAE to go
back to the old one, but mostly because I still have enough of the old one
available.
I straddle the old world and the new world, using the "old"
Please Google don't deprecate anything. Dont' introduce new parallel way
of doing things with new stuff and put the developers in confusion on the
dev roadmap.
Get back mapreduce. If I write a simple SAAS that is serving few customers
and growing, why do I need new and big and scary DataFlow
I will sorely miss Appengine, as it was a uniquely simple way to get
reliability and scalability.
And it was unique to Google. Other things, like containers, vms, and
databases, AWS also has them.
So I think the strategy is foolish. If Appengine is de-emphasized, I won't
be confident putting
It’s interesting to look at what Google is doing with Firebase.
1. They are encouraging us to move more of the processing into the client,
which while often architecturally foolish, does eliminate the need for some of
the PaaS stuff.
2. They have a serverless/cloud functions thing over there,
Anyone tried Beanstalk? Is it any better?
I’ve recently had a run-in with Azure where I had to store some stuff for a
customer in their S3-like blob store service. It was a nightmare. Insanely
over-engineeered to the point that it becomes impossible to figure out how to
do the simplest things.
I'll whine a lot, but there's a concentrated and crisp TL;DR in the end
I've been using App Engine I guess for 10 years now? It's hard for me too,
but also, I'm preparing to open source my current project, at each step I
question everything, I was going to open source my game so young
12 matches
Mail list logo
