Dear Google Cloud: Your Deprecation Policy Is Killing You

Post by EE84M3i » Sat, Aug 15, 2020, 4:58 PM UTC

manquer wrote: post #269

micimize wrote: post #252

Earlier quoted context omitted.

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…

Google are not competing with DO for developer mindspace, for large enterprises stability matters a lot more than new features and enterprise support matters too, for startups serving enterprises they don't do much either, what's left is consumer focused companies like SnapChat who can thrive on just innovative new tech. I can get Microsoft on a call anytime, I have account managers responsible who talk to me atleast…

Post by rvnx » Sat, Aug 15, 2020, 5:01 PM UTC

mauricio wrote: post #209

Wandfarbe wrote: post #207

Earlier quoted context omitted.

People have to realize, that software is not done when written. Software makes the fabric between everything in our lifes. It brought us tones of innovation; It is one of the biggest enabler, innovation drivers and tool we have. It is one of the complexest and cheapest tools we have. You know what happens with software which is stoped being worked on? Very old, unflexible Cobolt Software on Mainframe systems in banki…

People realize this, especially on HN. The post is referring to deprecations. You can patch security vulnerabilities and move a product forward without deprecations. Google does it well with Go.

Post by thethethethe » Sat, Aug 15, 2020, 5:03 PM UTC

wh-uws wrote: post #13

lowiqengineer wrote: post #2

The answer to why this is, I’m beginning to realize after talking to dozens of Googlers working at Google as acquaintances, friends, former coworkers, HN comments and twitter personalities is - Google has an active disrespect if you’re not part of their in group . If you haven’t passed their tests, you’re basically an object of derision - a mark, an object just used for incrementing a CPM metric, or an incompetent, l…

(warning rambling rant) I feel like this was super true in the pre Facebook days but they were humbled A LOT by the massive flop of Google plus. I honestly don't feel like I get the my s * doesn't stink vibe from them anymore. Especially because everyone knows their Achilles heel now. But for their ad revenue what would they be? Everything else material from came from an acquisition or is infra stuff. It's cool but t…

Post by john-shaffer » Sat, Aug 15, 2020, 5:07 PM UTC

joepie91_ wrote: post #154

dutchmartin wrote: post #142

Earlier quoted context omitted.

I strongly feel that you must have end to end tests while using node because of the dependency hell. Not even knowing if a upgrade of a dependency breaks your system is just hard. Also testing it by hand is just not maintainable.

> Not even knowing if a upgrade of a dependency breaks your system is just hard. This is true for any language/platform.

Post by yjftsjthsd-h » Sat, Aug 15, 2020, 5:08 PM UTC

Aperocky wrote: post #227

jedberg wrote: post #219

And then there is AWS, which has depreciated exactly one service, SDB, but only after they created a much better replacement (DynamoDB) and offered to help migrate all of their large customers, so they could get the usage percent so low that almost no one was affected by the shutdown.

Disclaimer: AWS SDE The focus on consistent behavior and once launch, never deprecate practice has caused many headaches, I personally know of control planes specifically written to accommodate old behaviors that a few customers had years ago even when the entire service has been updated. But IMO this is still much better than deprecating production services and behaviors on the fly.