[ohsnapman]

I'm not convinced CIOs are thinking about Reader or Wave. Before entering a big deal, it would make sense for people to read the deprecation policy. Unfortunately, the Cloud Platform deprecation policies are unclear.

The terms of service (https://cloud.google.com/terms/) point to the cloud platform deprecation policy (https://cloud.google.com/terms/deprecation). The Cloud Platform deprecation policy points to the product launch stage page (https://cloud.google.com/terms/launch-stages), which points back to the "deprecation policy" section of the terms of service!

As a CIO, I would be most concerned with the ecosystem and availability of talent. Google have done a good job trying to reuse some of the same tools and ideas like reuse boto, but writing scripts for their cloud platform vs. AWS is still as different as English and Dutch.

[saurik]

Google has shut down much more than Reader and Wave, or drastically change the paradigm or pricing of their existing offerings in ways that can drastically increase costs. Here is a link to a comment I wrote a year and a half ago, looking at Checkout and Charts.

https://news.ycombinator.com/item?id=6518473

(Note one correction: at the time, the deprecation of OpenID had no migration path; I complained to a bunch of people at Google I/O, as did likely other developers, explaining in detail the migration problem, and sometime in 2014 Google corrected this mistake.)