> Maybe that hasn't affected you yet, but the available evidence says that it has burnt plenty of people.
What evidence are you referring to here?
What evidence are you referring to here?
That alone is more than enough to substantiate what I'm saying, but if you need more examples than just search or read HN a bit, due diligence, etc. I was personally lucky in that I got burned in the planning stages and didn't have to get burned in production, but I still wasted all that planning time and ended up having to use AWS instead.
GCP doesn't seem to provide a full list of deprecations, but the list for just one service[1] is pretty terrifying when you consider that your app might depend on two or three dozen services, and a deprecation in just one of them forces you to rewrite perfectly good code. A cursory search reveals a number of reports of being repeatedly bitten by deprecations[2][3][4], so no one should be mislead by the dismissals here. [2] has a good cautionary tale of a forced "upgrade" leading to potentially much greater cost.
[1] https://cloud.google.com/appengine/docs/deprecations [2] https://nilsnh.no/2019/11/09/managing-the-google-cloud-platf... [3] https://www.slideshare.net/async_io/lessons-learned-from-bui... [4] https://www.lastweekinaws.com/podcast/aws-morning-brief/whit...
I do think Google Cloud is trying to do better and the few deprecations I’ve seen personally have been heavily scrutinized and considered, with a clear migration path for users. I was only asking for data to objectively understand the problem as it stands today, and not to minimize your own experience. I know there are experiences similar to yours, but hopefully there are far fewer in recent years (but its always hard to tell without data).