181–190 of 251 posts
Earlier quoted context omitted.
I’m not familiar with any GCP service being discontinued. Do you have any examples?
It never reached general availability, but remote-build-execution was discontinued.
[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 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 you could shelter your team's product?
Earlier quoted context omitted.
Concerning the promotion thing, I hear this a lot from Googlers but isn't it the same everywhere else? Most tech companies (big tech at least) will promote on product achievements, not maintenance.
The main difference was/is that at Google your immediate manager, director, PM, peers and everyone else in your product unit (who you work with every day) have almost zero say in whether you get promoted or not. You have to essentially summarize everything you did in bullet points and send it over to an anonymous committee who don't know who you are. They will base their decision on this piece of paper without any ad…
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…
Google can’t keep that up forever. It killed plenty of other cash burning projects.
Earlier quoted context omitted.
I just completed a migration from AWS to GCP. My experience was previously entirely AWS, but GCP has been really nice. GCP has fewer features (e.g., no scheduled filestore backups), but GKE is far and away better than EKS and the overall console UX is far better as well. There’s also generally less to understand and thus misconfigure, and far fewer half-baked features to wade through to find the happy path (I’ve spen…
I feel you on Cloudformation :S I haven't used Kubernetes on either platform - so there may be more to that. One thing I really dislike about GCP is how expensive it is for personal or hobby use. I burned through $300 for a simple vm on GCP in a few weeks because their cheapest instances are so expensive.
How'd you manage that? My bill is always super lower every month.
Earlier quoted context omitted.
> Admittedly, the original author's title of "Why I distrust Google Cloud more than AWS or Azure" much better describes their position than the editorialized title of the HN submitter ("Why Google Cloud is less trustworthy than AWS or Azure"). Agreed. What is with the retitling?
Submitter (& author) here. I just changed the submission title to exactly match the original.
common in other cloud environments, they just give you a longer runway / head's up on it
2) price increases
true
3) shitty customer service
same as azure and aws -- google, though, have a crap reputation to begin with. With the other two, it was a surprise.
4) continued existance of google cloud
article is over a year old; and - frankly - aws is likely to spin-off from amazon sooner than google cloud being shutdown
no sources, that is just my gut feel.
The market is easily large enough to have 4 - 6 global players *AND* 2 - 3 regional / country-specific ones as well.
The single biggest concern I have with Google cloud, bigger than Reader or the like, is Project Maven. What if some Google employees decide my company is bad? Will Google cave in and fire us as a customer? That’s an existential risk.
I can definitely see this being an issue if your product bombs funerals, helps regimes cover up human rights abuses, or deports undocumented people. Fossil fuels are a maybe. This really shouldn’t be a problem for 99% of customers though.
Earlier quoted context omitted.
It never reached general availability, but remote-build-execution was discontinued.
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.
Earlier quoted context omitted.
That's because Google's quota increases are binary: - either they're automatically approved because you fill in a form requesting more and it just becomes a PR for an engineer to approve, OR - it can't move because you've hit an internal service limit
Wait, really? Quota are recorded by code that must be changed by pull request, not an entry in a db? That sounds like an insane waste of engineer time.