[deleted]
Dear Google Cloud: Your Deprecation Policy Is Killing You
71–80 of 417 posts
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#72Earlier quoted context omitted.
I've never been hired or approached by Google. However, as a University lecturer I know a lot of people Google have employed. In my opinion, they have rejected some of the greatest students I have ever taught, and accepted some idiots who know how to speak well. While they have employed some good people, I believe they purposefully taret the type of people who think working at Google makes you a fundamentally better…
> In my opinion, they have rejected some of the greatest students I have ever taught There's no question that Google is happy to have false-negatives in interviews. > I believe they purposefully taret the type of people who think working at Google makes you a fundamentally better person than anyone else why would they do this? And, if they do this, how are they generally speaking so successful? (this is also an amusi…
And, if they do this, how are they generally speaking so successful?
The usual recipe for success in tech: competitors who are even less competent.
See also: how Microsoft dominated personal computing back in the day.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#73"GNU Emacs, which is a sort of hybrid between Windows Notepad, a monolithic-kernel operating system, and the International Space Station."
The article was worth a read for that quote alone.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#74I'd be interested in some concrete examples of things GCP have depreciated. I'm an (admittedly fairly light) user of GCP and haven't come across any myself.
Personal experience: I have to support an internal tool for a company in app engine. The contract is part time and I have to prioritize what issues to fix. The answer is usually "those caused by Google deprecating something". The nosql db some hyped individual has chosen years ago - "deprecated, we don't bother with solving bugs there". Email service: "it is in python2, but not in python3, look for management approva…
Dataflow SDK libraries have updated their minor version from 2.4 to something like 2.16 in just two years. Guess what, everything below 2.14 is deprecated and not supported.
And yes. Despite these being minor version updates, stuff will break if you go from, say, version 2.9 to version 2.11.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#75I think Google couldn't do better, even if they wanted to.
The reason is the engineering culture and the promotion system. People expect to switch to new projects, and work towards to a promotion within 2-3 years. This shows in all products, and presumalby also the reason for the deprecation. New people come on the project, want and need to do a major overhaul, and do not have resource or incentives to support the old stuff.
The other half is that most projects are done efficiently by relatively small groups of engineers. I remember that Android Market was still a few people in MTV, with no payment possibilities outside of the US, when Apple already had significant revenue from apps. And that shows everywhere. I'd argue Google is incapable of tackling projects that require more than a few hundred people for more than 2-3 years.
But as a billion dollar company, that does not work. Throwing money at obvious new billion dollar opportunities like Microsoft did with gaming and cloud, and following through over 5 years is not possible for Google.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#76I can hear cries from tenderfoot developers whining about supporting multiple options and backwards compatibility... "But that's sooooo muuuuch too teeessstt!! Whaaaaaaaaaaaaaaaa!!!!!!!!!!" But that's your job dude. So what if it costs more money and time. Fucking pay for it anyway. I feel like startup software dev needs a swift kick in the ass or three with that phrase.... "do it anyway!" Who fucking cares if these…
You didn't read the article, did you? Startup developers don't mind supporting multiple options and backwards compatibility. Often they have to because they don't have the time and the money to rewrite everything, so it's common in startups to run and support multiple versions of APIs, clients etc.
It's Google who doesn't provide backwards compatibility, upgrade paths and migration options.
> But that's your job dude. So what if it costs more money and time. Fucking pay for it anyway.
So why doesn't Google pay for it anyway?
> I feel like startup software dev needs a swift kick in the ass or three with that phrase.... "do it anyway!"
You mean Google devs.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#77Clearly author is making things up - there were no gummy sharks in micro kitchens. Sergey spoke at lengths about this.
> I considered using Google Cloud Bigtable for my online game, but it costs an estimated $16,000/year for an empty Bigtable on GCP. I’m not saying they’re gouging you
Ok, but they are
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#78I have personally used a large number of cloud compute services: AWS, packet, Alibaba, Digital Ocean, nimbix, Azure, Oracle, ... I still use all of these services from time to time. If you carefully look at my list of cloud vendors you realize that there is only one of the big cloud vendors missing: GCP. Why?
When GCP came out I wanted to switch from AWS to GCP because AWS was costing me a lot of money and GCP was marketed as being cheaper. So I went to their website and signed up. Or at least I tried to sign up, because GCP did not care about individuals, you had to be a company! No other cloud vendor I tested had this requirement! So up to this date I have never tried to sign up with GCP again.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#79Earlier quoted context omitted.
You missed this: > I’ll also give a shout-out to our friends in the Operating Systems business: Windows, Linux, NOT APPLE FUCK YOU APPLE, FreeBSD, and so on, for doing such a great job of backwards compatibility on their successful platforms. I share your desire for stability. I don't necessarily mind frequent updates for security reasons, but I'm getting to the point where if things are changing in big ways often, I…
OK but he talks about how Android OS has had backward compat for over ten years, but Windows has been doing it far longer and with a much bigger OS and more complex hardware base.
That's because he has much more detailed knowledge of Android's backward compat story than he does of Windows's.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#80> [Google] contracted with a company called Bitnami to create a bunch of “click to deploy” solutions, or perhaps I should write “solutions”, because they don’t solve a fucking thing. They’re just there as checkboxes, as marketing filler, and Google never gave a shit whether any of them worked from Day One. I've had similar experiences with broken Bitnami images that makes it seem like they aren't even tested before b…
Bitnami broke their MongoDB Helm chart. We're careful to pin versions, and hadn't anticipated someone would re-write history and break published code.
Can't get too upset, we don't pay them anything. Not in a rush to use them again though.