Live data from Hacker News

Why I distrust Google Cloud more than than AWS or Azure

iasylum.net

191–200 of 251 posts

Re: Why I distrust Google Cloud more than than AWS or Azure

#191

Earlier quoted context omitted.

And the odd thing is that Google has been significantly better for consumers than other FAANG companies. Apple has historically been anti consumer and anti developer with a huge marketing budget to wash it. Facebook intentionally makes us sad. M$ and their anti competitive practices should be well known.

> Apple has historically been anti consumer What? Apple has been pro-consumer to the detriment of everyone else. Developers are still screaming that they aren't allowed to install malware on my iphone.

That works both ways though: I'm not allowed to install anything I want on my phone, which is anti-consumer.

Re: Why I distrust Google Cloud more than than AWS or Azure

#193

I'm not sure what the author (or Yegge, for that matter) expect a good timeframe to be for deprecating services. Anecdotally, Google announced the changeover of Cloud logging API versions in October of 2016, with a 5-month ramp (October to March) to switch from the v1 beta API to the v2 beta API. Five months is nearly two quarters, which is quite a long window for a beta API IMHO. That having been said, Google's habi…

When I was doing deprecations on GCP, it was minimum 12 months for any deprecation. Five seems shockingly fast! As for the beta thing: GCP's definition of beta was basically everyone else's definition of GA, since the GA requirements were so insane (e.g. 99.999% internal availability) that getting there would take literal years (see the GCF beta to GA taking like 18 months?). I totally agree that it's weird that thin…

I can vouch that’s not a true statement. The deprecation policy doesn’t cover breaking api changes. Forced k8s version upgrades.

Among other edge cases that caused pain.

Re: Why I distrust Google Cloud more than than AWS or Azure

#194
post #189

Earlier quoted context omitted.

RBE was discontinued during alpha. They tried a thing, it didn't work out for some reason, so they decided not to bring it to market. This hardly fits the bill of the typical Google deprecation.

Is it really accurate to call it an alpha when there are paying customers?

Not familiar with RBE in particular, but as a rule alpha/preview services are free.

Re: Why I distrust Google Cloud more than than AWS or Azure

#195
post #127

While I'm not arguing the general point of the article, I will counter point one thing. > Will Google Cloud even exist a decade from now? This seems wildly speculative, and the likelihood of GCP, or its core offerings, not existing any time so soon is next to zero. Google has to royally fuck up for this to be the case, but even if it ends up being case, there will be a string of lawsuits lined up that will likely cos…

There were multiple companies forced off Google Maps because of a pricing change. This could absolutely happen and has happened before.

That's very different from Google deciding to shut down Maps.

Re: Why I distrust Google Cloud more than than AWS or Azure

#196

[DISCLAMER: I used to work at Google in general, but not at Google Cloud] I'm not sure whether this has been discussed here before, but I'd love to take this forum to share an angle from the tech side of things: IMO, Google is _cursed_ to keep deprecating its products and services. It's cursed by Google's famous choice of mono-repo tech stack. It makes all the sense and has all the benefits. But at a cost: we had to…

As an outside person - Why can’t Google support services for longer, and hire more engineers for fixing up stuff? There surely is enough budget?

Re: Why I distrust Google Cloud more than than AWS or Azure

#197

[DISCLAMER: I used to work at Google in general, but not at Google Cloud] I'm not sure whether this has been discussed here before, but I'd love to take this forum to share an angle from the tech side of things: IMO, Google is _cursed_ to keep deprecating its products and services. It's cursed by Google's famous choice of mono-repo tech stack. It makes all the sense and has all the benefits. But at a cost: we had to…

I worked as a SWE at Google and also at Google cloud. I both disagree with this and find it a very perplexing angle. I think the issue is a mis-aligned (financial) incentive structure. With the right incentive structure, challenges in either monorepo or federated repo can be overcome. With the wrong incentive structure, problems will grow in both monorepo and federated repo. The choice of repo simply manifests the wa…

Was customer satisfaction a performance goal?

Re: Why I distrust Google Cloud more than than AWS or Azure

#198

[DISCLAMER: I used to work at Google in general, but not at Google Cloud] I'm not sure whether this has been discussed here before, but I'd love to take this forum to share an angle from the tech side of things: IMO, Google is _cursed_ to keep deprecating its products and services. It's cursed by Google's famous choice of mono-repo tech stack. It makes all the sense and has all the benefits. But at a cost: we had to…

That sounds sad. Why doesn't Google do something to become more nimble?

Re: Why I distrust Google Cloud more than than AWS or Azure

#199
post #182

[DISCLAMER: I used to work at Google in general, but not at Google Cloud] I'm not sure whether this has been discussed here before, but I'd love to take this forum to share an angle from the tech side of things: IMO, Google is _cursed_ to keep deprecating its products and services. It's cursed by Google's famous choice of mono-repo tech stack. It makes all the sense and has all the benefits. But at a cost: we had to…

> Would have save 90% of that person's time it it's on a sperate branch and we only need to focus on security patches. (NO, there is no such concept of branching in Google's dev system). I wonder if this is why you have so many different programming languages being used under the hood at Google? Essentially people using a programming language as a branch. If you're working on a completely different language in theory…

I'm not sure if agree. Almost everything major is written in Java or C++ still. And I'll disagree that the issue is with libraries at all. It's with other services changing out from underneath you.

Re: Why I distrust Google Cloud more than than AWS or Azure

#200
post #134

[DISCLAMER: I used to work at Google in general, but not at Google Cloud] I'm not sure whether this has been discussed here before, but I'd love to take this forum to share an angle from the tech side of things: IMO, Google is _cursed_ to keep deprecating its products and services. It's cursed by Google's famous choice of mono-repo tech stack. It makes all the sense and has all the benefits. But at a cost: we had to…

I have also worked at Google (in an unrelated department) and completely disagree with this. Maintaining old code & services is a problem everywhere. Monorepo vs multirepo, monolith service vs microservices etc. all have nothing to do with it. There will always be a broken dependency, a service/API/library you rely on about to deprecate, new urgent security patches, an outage somewhere upstream or downstream which yo…

I think monorepo makes it easier to update downstream dependencies atomically as part of an upstream change, and thus encourages a culture of unstable APIs.

That is, careful evolution of internal APIs is not given much weight, so modularity - in the sense of containing change - suffers.

I don't think monorepos must necessarily go this way, but expressing dependencies in terms of build targets rather than versioned artifacts has a strong gravitational effect. Change flows through the codebase quickly. That has upsides - killing off legacy dependencies more quickly - and downsides, wanting to delete code that isn't pulling its weight because of the labour it is inducing.

[I currently work at Google but I've only been here a few weeks. I certainly don't speak for the company.]

Post reply on HN