Organizationally, domains was not part of cloud. It's part of shopping which is closer to ads and search. I don't see the correlation between this and turning down cloud.
Seriously, customers don’t care about the internal nuance of how things are organized. They care that a very foundational piece of a cloud service provider will suddenly be not available.
Seriously. Comments like the one to which you responded are absolutely endemic on this site. Like half the people here are incapable of viewing anything as a non-expert.
Aren’t the people that use GCP the voices that you should listen to? The 2-back comment is basically hearsay while the 3-back is from a presumed GCP customer. I also use GCP and this stings a little, but I’ve never otherwise seen a single component in GCP deprecated, which is why I continue to use GCP.
GCP customer here as well and while this does make me a bit wary, I'm not too ruffled yet. I really love their cloud console UI and how they organize things and have been nothing but happy with their cloud services. Hoping it stays that way!
> Organizationally, domains was not part of cloud. It's part of shopping which is closer to ads and search. I don't see the correlation between this and turning down cloud.
It seems like you're saying that since Cloud Domains relies on Google Domains which wasn't organizationally part of GCP (even though there's no way a user would have known that) it is acceptable to shut down Cloud Domains when Google Domains is shut down and that doesn't mean that google isn't committed to supporting GCP.
This argument is just completely baffling to me.
If it turns out that Compute Engine relies on some internal services that aren't organizationally part of GCP does that mean it's fine for google to shut down Compute Engine as well?
