Manager for Google cloud platform inadvertently flags up weakness of cloud
I'm not sure how much it would have cost to keep these APIs active, but documented as 'deprecated'. My guess is not very much. It can be bad enough within a single company when interfaces change, and all clients using them have to be changed. Multiply that by potentially millions of systems that may need to be changed when a service in the cloud changes.
I have no problem with Google introducing new and better APIs in order to provide increased functionality. However the fact remains that a lot of stuff could potentially be broken as not everyone will be constantly checking the availability of services (even though they should be). This had become much more of a problem with the amount of mobile apps out there which I'm guessing mostly call third party APIs directly and would therefore need updating on every single device running them (and what a waste of bandwidth thatr is). It shows that for any non-toylike apps that make use of third party APIs, the only solution is to write these apps so they talk to an API that you host (in house, on cloud, wherever...) and have that call the third parties, so changes like this can be swiftly and easily managed.
Otherwise we will have moved rather unthinkingly back to the hellish time of 'clientserver' architecture of the mid 90s when most time was spent rolling out new versions of client software to every client and most support costs caused by lack of good version control and the helll of multiple client versions being in use, either deliberately or accidentally.