I have more confidence in Amazon and Microsoft.
Google sticks with things that are core. Google reader was obviously not core.
Glasses moved to enterprise and continue to be used in that setting.
I'm not saying it's better than other offerings - It's not all around - but the building blocks are really nice.
There is a lot to be said about choosing the default. I've been a .Net developer for over a decade, but when I started looking into Lambda for instance and saw that it looks like most people were using Node and to a lesser extent Python, I begrudgingly started learning Python. In hindsight, I'm glad I did. I'm actually starting to like Python and I usually hate scripting languages.
Besides, for my own selfish reasons, why would I spend time on the cloud platform that is the least marketable? Companies are asking for AWS and to a lesser extent Azure experience. Very few are asking for GCP experience.
If everyone is going one way, it's not necessarily a bad decision to take a slightly different path. I've been able to build a career and a business on the alternate path.
During those days UNIX based systems were just yet another option, mostly on government and university departments.
I learned UNIX thanks to our OS teacher carrying around a single PC tower (remember those?) with Xenix on it, where we would take 30m turns to try out our C programs, prepared in advance with Turbo C on MS-DOS.
80's and early 90's, before Linux and BSD actually took off as a free way (free beer) to get access to UNIX.
Further, Google has been taking the Google bits out of Kubernetes. They declined to call their own offering "Google Kubernetes Engine" officially until the playing field was level and they had a certification program. Amazon, Azure, DigitalOcean and others are implementing their own managed Kubernetes solutions.
Google doesn't have to cheat here. Speaking as someone dealing with Google Cloud directly, they are mainly hitting on the point that Google Cloud offers better network and disk performance, in a more flexible manner, for significantly less money. And honest to God they're right. The CPU performance is worse in some cases, but we're saving money on workloads so far.
On the flip side, as long time AWS users, the Kubernetes experience has been pretty good since Kubernetes 1.3. New features typically support AWS pretty early in, with the main exception being Ingress controllers (for good reason: ALBs weren't even released when that became a thing.)
Google is one of those companies big enough to make it easy to feel like they have evil ulterior motives, but I'll be honest: in my dealings with them, I've felt that the opposite is true and generally the intentions are good.