Funny how everyone here complains about Google maps changing their licensing, but nobody brings up MS changing changing from per socket to per core licensing a few years ago. That burned several medium businesses I know.

Per socket vs per core happened with a version bump right? If Google maps pricing changes only happened when you used a new api, and you could keep using your existing code with your existing prices, that would be a lot less grudge worthy.

Are you talking about SQL Server? You can keep using old versions, and the performance improvements of modern hardware and new versions end up providing more value overall.

With Maps, there's suddenly a new price and you have no options.

Also Windows and System Center. It’s very painful for Microsoft shops as many applications really need standalone SQL.

With our scaled up SCCM environment, SQL alone increased licensing cost by a very significant factor, as you need to license SQL Enterprise when you exceed the core limits of the gratis SQL Standard license.

Probably not a lot of people used Microsoft services then.

Google maps is NOT a part of Google cloud!

https://cloud.google.com/products/

This is not correct: https://cloud.google.com/maps-platform/

Google Maps Platform is a part of Google Cloud, but not a part of Google Cloud Platform, despite now integrating with Google Cloud Platform's web console for purposes of managing billing and API keys. Yes, this is a branding and communication mess, but nevertheless true.

You seem to be correct.

> Google Maps Platform is a part of Google Cloud, but not a part of Google Cloud Platform

I have never felt that I have been confused by something so justifiably.

(googler working in gcp here)

The basic way to tell if something is part of GCP or another Google product that some marketing whiz managed to have "cloud" tacked onto the name is whether or not you need a GCP project to work with it.

(GCP employee)

Not true, as far as I know. Many (if not all) Google APIs require a GCP project for access via API key, service account credential, or mobile application.

Do you not for Maps? All my API keys are lumped under "test_prjoect_1" for me, which I don't even remember creating.

No argument here on that point!

I'll defend many things about the technical quality of GCP and its appropriateness as a viable choice in many cases, but not Google's branding, external PR, or external perception management.

They've always been bad in those areas and that pattern continues.

(Relevant disclosure I've said in other comments: I used to work for Google, including GCP, ending in 2015. I've never worked for Google PR/comms/marketing and I don't work or speak for Google now.)