Since you're checking notes, please check out all the AE service deprecation notes.
Disclosure: I worked for Google for ~10 years, and I fought internally many of those deprecation decisions. I did not succeed.
I see that as a good thing, it means they are still working on it.
My guess is not, or you would have a different opinion. But that's just a guess
My best friend Jeff started working on Objectify in 2009 after I convinced him to use GAE. I have built two businesses on it. One did $80m in revenue in the first year and I guarantee we couldn’t have done it without GAE.
Now give me back my downvote please.
You also just said that you used it very effectively back when it was a different thing.
I think we agree in many more ways than we disagree.
"We migrated"... meaning that over time, everyone is migrating from the concept of using GAE as a first choice, to using things like Run/Functions. Not that I actually physically took code for GAE and moved it to R/F. For example, my last project, I choose to use GCF, instead of GAE. The reason I went straight to GCF is because it is effectively what GAE has morphed into today. This isn't a slight on GAE at all.
Again, I have used GCP extensively since about 2009. By the way, much of what you use today was a result of things I did back when I co-founded the Jakarta Apache project, open sourced Tomcat from Sun, blah blah blah...
- In 2012 App Engine deprecated the "Conversion API".
- They notified this deprecation in August 2012, and they told users it would stop working only 3 months afterwards.
- You were affected by this deprecation.
- You created an alternative to it, that worked on Heroku.
Source: https://groups.google.com/g/google-appengine/c/-JJccGx5RRk/m...
Did I get this right?
You are awesome. We are just choosing to remember the past with different colored glasses.
There was a point where people were upset about GCP and Google changed their whole deprecation policies to be more vocal and longer term about things.
I really don't understand your point. What's the big deal?
Once enough things were unbundled from AE, and containers became popular, it wasn't really clear what AE provided that wasn't better solved by more standard tech.
Often times, Google leadership simply didn't understand what its own engineers and product managers knew. People told me for years "we can't do cloud because the profit margins are too small", and now look: Google is a perenially third-place in Cloud but has committed itself so much they can't even shut it down if they want to.
The problem with AppEngine was that they had to heavily modify the runtimes for isolation... the JVM needed to be secured and that meant maintaining a separate fork, which also meant being perpetually always behind in versions. It also meant any upgrade had to go through a huge security evaluation.
So, moving to another process model, containers, worked much better.
AppEngine is going on, checks notes, 15 years now.