[Justsignedup]

It gets to the meat and potatoes at the end. They were forced to do it, so they put a positive spin on it as if they're doing it out of the goodness of their heart.

Still a positive, but man, that marketing messaging. I give props to the team who wrote that.

[Havoc]

At least they acknowledged it in passing

Googles equivalent announcement was all flowery bullshit making it seem like a voluntary action

[AtlasBarfed]

That, friends, is a "tell".

It shows they know they are raking people over the coals with intentional, preconceived illegal anticompetitive behavior written into their documentation.

Right from the playbook, they have a sweet marketing wrapup for when they have to walk back their preconceived illegal behavior to the minimum directed border.

Tech corps especially now do this as standard operating procedure (I mean Uber had entire divisions and armies of lawyers to bypass/obfuscate/delay imposition of local cab and labor laws). It's why you can't trust them with AI, personal information, AI, customer service, AI, following laws, AI, or anything.

I know Google in the heydey of the aughts wasn't as "good" as they tried to be, but at least the "do no evil" kind of kept them in check to some degree. But at some point they bought the corporation-formerly-known-as-DoubleClick, and I think in retrospect that was the beginning of the end of functional idealism in the internet.

[Justsignedup]

The other comment mentioned how google didn't even acknowledge why they did it.

I have to say, talking to AWS and GCP, the AWS marketing, onboarding, and support arm are far far far far far superior to google's. In fact they are so far apart that our management has blatantly discarded google as even an option for moving our infra over because of how terrible our interactions have been. I'm all for de-throning the king, but it ain't gonna be done by the court jester.

In any case, point is, AWS has good strategy where it matters most.

[jnaina]

Agreed. Court jester is the correct phrase, as GCP are complete clowns. Some of the stories we know of, from our customers, about GCP's conduct and lack of any semblance of professionalism are shocking. MSFT/Azure on the other hand, are formidable and worthy competitors in the cloud space, against AWS.

[pm90]

Can you give specific examples of what was lacking? Ive only had positive experiences with GCP.

[Justsignedup]

We want to migrate to it:

"Okay cool! We'll sign you up! Good luck!"

vs

"We have a migration strategy, and partners who can help you lift-and-ship or at least consult to get you a lay of the land. Try these companies and see if you're interested, and we'll help you along the way."

Google is -- thanks for reaching out, you can certainly sign up and figure it all out, here's a few books!

Amazon -- things are complex, and here's a few books to read, but I know you don't have a few years so here's some people who know how to do this, and we've ironed out how most companies succeed in migrating. Also he's a ton of incentive to move to amazon-exclusive services.

[Max-Ganz-II]

I specialize in Amazon Redshift.

Speaking for and only for Amazon Redshift, as I have little knowledge of other AWS services, I hold AWS's blogs, messaging, Support communications, TAMs, the lot, as relentlessly positive and to my eye deliberately and knowingly obfuscating all weakness. I regard information from AWS regarding Redshift as safe to read when and only when you already know what's going on / the underlying truth. Otherwise you will be misled, and to your cost at AWS's benefit.

By the sounds of it, the messaging over this change in data policy is the same.

[therealcamino]

> "safe to read when and only when you already know what's going on / the underlying truth"

I've never read AWS blogs before but that was exactly my feeling after reading the linked article on "fair software principles" or something. You can tell that somebody has a hobby horse they're riding, and it's only because it's in their financial self-interest, but unless you already knew what the actual issue was before you read the blog, you're still going to be clueless afterwards!