Android is the top example of this by far, everything is half finished & deprecated.
Dear Google Cloud: Your Deprecation Policy Is Killing You
251–260 of 417 posts
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#252There are other tradeoffs between cloud providers that are important to keep in mind here. In my experience, GCP has been easier to get started with, and has offerings that are by-and-large more comprehensible. One thing I really appreciate is that a lot of their client libs have automatic auth within GCP (last time I used AWS this wasn't the case or I didn't know about it). As someone who hasn't been burned by it pe…
Easier to get started ? Their UI , IAM architecture and firebase being kind of separate is so confusing . Aws used to be simpler , while they are screwing it up now, the recent route53 upgrade was terrible , a single click action has now become 4-5 clicks they are still better than GCP. Azure has the really the best interface (outside of DO) , it is easy to go to related and nested resource in one freaking app. Both…
That's just been my experience – I remember having much more pains trying to get AWS IAMs and permissions to work, and I really like that they give you suggestions like "this machine could be smaller" or "this role never actually uses all these permissions."
Also I haven't worked _that_ much with firebase, but it seems like a great example of the benefit of using GCP. Firebase is a cohesive and accessible solution to a lot of what can be fairly nightmarish technical problems. This kind of thing will always depend on the project/team/team size, but I'm just trying to say that there are significant benefits to GCP that should be considered.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#253Earlier quoted context omitted.
Try to keep up with Android development and Play Store policies... I stopped publishing own apps on the Play Store, and unpublished all the one that I had, because of the stress and the time used just to follow the damn policies.
As an Android engineer, I'm not sure what you're talking about. There was a push to get people to move to the new permission model, but I believe that's still optional so long as you're willing to suffer with old SDKs
They're making it mandatory to constantly bump your targetSDK.
They're adding new requirements one has to follow in order to get access to certain permissions.
They're updating their content rules which make anything with user content very very difficult and might just kill your app one day.
They're updating graphics and icon requirements rather often.
It's a rather big amount of work if your app isn't super simple and relies on functionality they change.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#254[deleted]
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#255Google is an absolutely fantastic company from which to get free stuff. Gmail, Maps, Docs, Youtube? Mmm-mm good! Buy things from Google, though? You mean, give Google money and in exchange expect them to adhere to some kind of standard of behavior, support, and customer service? Go get a coffee because you're clearly not awake yet.
This is the exact opposite of the usual complaint: that if you don't pay for support you can expect Google to arbitrarily shut your account and scoop up all your data - however paying them actually allows you some control.
Many of the frequent horror stories on here about account suspensions and completely unresponsive support are coming from people or companies with paid accounts.
I do believe that there is a level of spending where you can actually get a hold of someone competent who can look into things. But that level appears to be rather high.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#256> Let’s say hypothetically that Apple was dumb enough to pull a Guido van Rossum, and declare that Swift 6.0 is backwards-incompatible with Swift 5.0, much in the way that Python 3 is incompatible with Python 2. Damn, I was waiting for this. The whole essay was a setup for this paragraph. Reframes the argument using a shared traumatic experience for everyone. This humanizes the effect, we all know someone that lost s…
I don't get the Python3 bw-incompatibility hate. Getting rid of cruft is literally the only way to get rid of cruft. It's literally the Pythonic to not have cruft.
I dread the day Python will be as bloated as C++ or Java, neither that dare to remove things.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#257It is a total hassle to keep up with Googlers changing everything constantly. It's not just GCP it's every platform they control. Try keeping a website on the right side of Chrome policies, a G Suite app up, a Chrome extension running. Thousands of engineers chasing promotions by dropping support for live code. If it was their code they wouldn't do it. The org is broken. If you want to see what mature software suppor…
> Win32 binaries I wrote in college still run on Win 10.
Hell they said they were dropping support for VB6 in Windows 8 if I remember correctly, but I'm pretty damn sure I can still install the IDE, I know VB6 apps aren't broken for darn sure since I've re-downloaded some old ones I used to use.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#258It is a total hassle to keep up with Googlers changing everything constantly. It's not just GCP it's every platform they control. Try keeping a website on the right side of Chrome policies, a G Suite app up, a Chrome extension running. Thousands of engineers chasing promotions by dropping support for live code. If it was their code they wouldn't do it. The org is broken. If you want to see what mature software suppor…
I'm reminded of a blog post I once read, which annoyingly I now cannot find, on how the job of a library maintainer is to not break the API. If you break the API, you've failed at your job. This mindset makes more sense than treating API breakages as a routine case-by-case decision. As the article puts it, breaking changes are breaking the library's commitments. (The library/service distinction doesn't matter much he…
Agreed, that is probably why you wind up with a lot of versioned Microsoft C++ runtime installers on your computer, but damn it at least the reliant software works as intended.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#259Earlier quoted context omitted.
I don't have the same issues as your colleague. I've been using Azure for 8 years and rarely run into any issues. Maybe his issues isn't with Azure.
I have heard similar from more than one person. Maybe it depends on the services you use.
Or, perhaps, the particular SDK you use to access their API?
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#260Earlier quoted context omitted.
the main thing here though is the older things you’re moving away from in those cases are still around. AWS didn’t remove classic load balancers and force you onto application load balancers.
Agreed. But they did deprecate EC2-Classic. "The EC2-Classic platform was introduced in the original release of Amazon EC2. If you created your AWS account after 2013-12-04, it does not support EC2-Classic." https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-clas...
> after 2013-12-04
That was 4 years after VPC was launched. So yes, while they do deprecate stuff on the rarest of occasions, they still give you much, much more time than GCP ever did.
Also, EC2-Classic is still available if you reach out to your TAM with a really good reason.