Disclosure: I work for Google.
To the best of my recollection, I don't believe we've ever shutdown a product. Was there one in particular that hit you? (Reader, Wave, etc are totally different divisions.)
To the best of my recollection, I don't believe we've ever shutdown a product. Was there one in particular that hit you? (Reader, Wave, etc are totally different divisions.)
So yeah, I think it's entirely their fault.
so while "google" might have funds, the "google code development team" may have a very tiny allocation.
Even if they had been trying.
But yes, like many Google products, it was basically released and abandoned. They weren't trying. (If they had been, maybe we never would have had a github...)
I do think as a public service, they could have left all the code (and wiki documentation) accessible read-only virtually perpetually. Surely they can afford that.
Instead, we get tarball download only, and only until late 2016, after which it's all gone forever, if it hasn't been migrated elsewhere by code owners or third parties.
But it is more common for a Google product to be completely abandoned, no new features, few bugfixes, etc., as opposed to being actually shut down.
There's a long, long list of Google products and services that have been discontinued, as somebody else already linked to in this thread: https://en.wikipedia.org/wiki/List_of_Google_products#Discon...