Dear Google Cloud: Your Deprecation Policy Is Killing You (2020) • Hacker News Board

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#121

Post by [deleted] » Fri, Oct 27, 2023, 1:21 AM UTC

scarface_74 wrote: post #120

zmgsabst wrote: post #118

Earlier quoted context omitted.

There is no technical requirement to use a Lambda to integrate Salesforce — feel free to cite contrary information. https://help.salesforce.com/s/articleView?id=sf.integrate_wh... > But you’re so concerned with “cloud lock in” and you completely ignore the other 200+ services that the average enterprise is using. Why are you so concerned with the cloud, but not Salesforce, ServiceNow, Sharepoint, Okta, Azure AD, etc?…

You did see the part about integrating Salesforce with a Connect call center didn’t you? So I’m an “incompetent developer” who someone managed to get hired at AWS Professional Services not a third party partner - you to consult the largest organizations on the planet? I’m sure an AbstractFactoryRepositoryFacade is going to prevent cloud lock-in while you advise people to create a complicated workflow when a simple SQ…

[deleted]

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#122

Post by jay_kyburz » Fri, Oct 27, 2023, 1:37 AM UTC

Terretta wrote: post #119

jay_kyburz wrote: post #117

Earlier quoted context omitted.

Oh we are posting emails. Here is one from google I have been ignoring because updating the app is so far down my todo list it will just never happen. ======== This is your final reminder: By November 1, 2023 version 4 will be deprecated and any updates to existing apps will first require you to migrate to PBL version 5 or newer. We are sending you this reminder as one or more of your apps is still using Play Billing…

Working for two years is "future-proof". Says as much in a few words as the original article.

To be fair, this email doesn't say they are going to stop collecting payments, or that they will remove the app from the play store, only that I will not be able to update it. And given I haven't updated this one is a very very long time, its not really a big deal.

I would be more upset if they actually remove the app from the app store. I'm looking at you Apple.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#123

Post by Brian_K_White » Fri, Oct 27, 2023, 8:22 AM UTC

UncleMeat wrote: post #96

Brian_K_White wrote: post #81

Earlier quoted context omitted.

"My experience is that people really do become proud of the systems that they build and that deleting them is something they avoid." Who is still in the same position or team 10, or even 2 years, or even 6 months later, especially in any faang?

I have been on the same team, maintaining the same system for 10 years here at Google. The median tenure on my team is six years.

That is good to hear. I had gotten an impression of frequent moves required as the only way to advance.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#124

Post by rldjbpin » Fri, Oct 27, 2023, 9:26 AM UTC

personal anecdote: used dialogflow (when it got rebranded from api.ai after getting acquired by Google) to create a chatbot in 2018.

funny to track how it got placed inside Google's AI offerings since. i may have missed a few, but it got moved inside their GCP suite of offerings, and now lost somewhere in Vertex GenAI offerings probably.

advancements happen and i understand that. but when your entire platform to achieve x changes drastically within a span of a couple years, how can we consider creating stable systems like of the past with XaaS model?

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#125

Post by anuraaga » Fri, Oct 27, 2023, 10:16 AM UTC

Don't think I see much in terms of new content here so to add an anecdote about a deprecation post-dating the OP:

My wife and I created an app using the GCP Maps Platform for Unity (or some name similar to it, it was definitely a GCP project) 2-3 years ago. It was for an exhibition, not a long term project though there were aspirations to maybe do something like that. But exhibition ended, and a year or so later the API was sunsetted.

Fast forward to just last week, phones have changed since then, and she wanted to rebuild the app to demo it. I had to say nope, API's gone... But we're lucky to have not actually gone forward with trying to build a business on this despite there definitely must have been people that did and had to migrate to self hosting by force.

Still I use GCP, the UX compared to AWS is just much better, both the APIs (i.e. Terraform) and console (no region!!!). I do know the typical Googler personality and suspect server features like Cloud Run are safe while anything too close to application like analytics is at risk and I'll generally avoid it. I do wonder where auth falls on this spectrum, I'd like to avoid auth0 etc since just too expensive, but it is a bit hard to trust after seeing a shutdown of an app feature.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You (2020)

#126

Post by DrScientist » Fri, Oct 27, 2023, 11:05 AM UTC

UncleMeat wrote: post #57

renegade-otter wrote: post #47

Earlier quoted context omitted.

Google culture in general seems to be "this is not fun or a very profitable, so we are just going to, like, not do it anymore". Fundamentally it comes from the fact that they don't have to do any of it anyway . Anyone using AdWords knows that it's a money-printing machine. Google is thousands of fresh CS graduates who want to do "cool green-field stuff" but not really the day-to-day grind we are all part of and what…

I think that there are competing cultures, and ultimately only one of them has the power to fire people. I'm currently losing a multi-year long siege to kill a project with significant external visibility almost entirely because of organizational structure. A series of reorgs and new VPs have ended up such that our VP doesn't give a crap about our project and the VP that does doesn't have a great relationship with ou…

I think the other problem with reorgs is that the incoming VP often wants a success they can call their own.

It's a bit like lion infanticide when a pride is taken over - the new leaders are not invested in existing projects - they want to give birth to a success of their own and your maintenance of an existing project is competing for resources.