If you have no problems, it's fine. The first time you need to call customer support, you start wondering if TMobile or somebody else would be a better provider.
Google, on the other hand, pretends to be a good provider of lots of software services, but if anything ever goes wrong with any of them, you are screwed, including if it's a premium service that you pay for. This is why you should never allow Google to control anything that is important to a business of yours or to your personal life.
Google has tons of sales reps on the ad side who will be happy to give you a rationale on why you should spend money more aggressively on their platform, but even they will sometimes be useless at fixing problems unless you are a truly massive customer for them. If you ever need to talk to a sales rep, you can get a Google ad person on the phone in minutes, but they will tell you to bid more aggressively and to buy more display ads.
If your problem with Google is that you aren't spending enough money on display ads, they're Johnny on the spot; they've got 9 trillion hammers that they want to sell you for that particular nail. Need help with anything else substantial related to a Google service? We have a robot you can e-mail for that, and that robot will ignore you.
On that note - I have AT&T. I'm fine with AT&T, except that group MMS / messaging is broken with non-iPhone users. I've tried calling support, walking into a store, and now - simply given up. I tried two other carriers a few years ago, and had far worse problems, so I just suck it up and call people when we have to communicate. At least that part works.
You sum it up well.
When AWS first arrived they had the same automated support system that Google does, and they didn’t really want to comply with GDPR. We probably would’ve gone with Azure anyway because it’s the easy option for operations when you’re already in bed with 365, but the Amazon/Google attitude meant they weren’t even considered beyond the first look.
Since then AWS has overtaken Azure in GDPR compliance and the availability of their support, and we now have several supplier operated solutions in AWS.
Google is still on the “do not buy from this company” list.
But maybe they just aren’t interested. They are primarily an advertising company after all.
They didn't have exactly what you wanted so provided a workaround that would solve the problem.
https://tedpiotrowski.svbtle.com/switched-to-verizon-iphone-...
Google is AT&T: technically great, but customer support is intentionally and aggressively incompetent.
AWS is Verizon: technically good with some weird rough edges and legacy stuff, but customer support will bend over backwards for you.
Does that mean Azure is T-mobile? I have little experience with either.
A couple years ago, there was an update that affected a bunch of embedded devices and caused some machines to go down. Luckily our machines were on an older version, but another shop we worked with got hit by it.
Within an hour of Microsoft being alerted to the issue they'd begun working on the problem and within two hours machines were back up and running again after Microsoft pushed an update.
Yes? If you can't trust your rep to give accurate recommendations, then what's the point of even having one?
The cumulative time if took them to read and answer all of those emails (and cost) was definitely double that of just shipping the $1 part.
I have never heard anyone say that the AWS toolset was anything but "an amalgam of individual projects developed separately." It is obvious from their UI that the different tools are run by different teams that have very different opinions on how things should be done. Just look at the various iterations of deployment management. ECS vs Lambda vs EKS vs classic EC2. All the UIs have different design standards and assumptions. It has gotten better over the years, but the AWS org chart is still peaking through the UI.
GCP is not much better. At least they had the advantage of starting later in the market cycle. They were able to see what worked and what didn't work at AWS and build a bit cleaner.
In the end we are talking about B2B systems targeting power user engineers. The control surfaces need to be powerful first, and easy to use is a distant second or third consideration.