well, google isn't a small business, where "the budget" can be synonymous with "the bank account(s)". like many (all?) large businesss, things are organizationally regimented into units (and sub-units, etc), and budgets are allocated toward each unit.
so while "google" might have funds, the "google code development team" may have a very tiny allocation.
Of course, but budget allocation does not descend from Heaven fully formed, so to speak. Google directors (i.e. Google) decided Code was not a priority, so in the end it's Google-the-company's fault that it had to close.
Re:Google Cloud Shell
by jrochkind1 on Wednesday October 07, 2015 @07:04PM
(#10349760)
I think there was no reason for them to keep Google Code as a going concern with the rise of Github. They were not going to do as good a job as Github, and it wasn't something they were making any money off of.
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.
So yeah, I think it's entirely their fault.