Google is not your daddy: long term reliance on APIs is as bad as outsourcing
webiphany.com
webiphany.com
The article is not about APIs of libraries.
On the other hand, Google has clearly gone the way of flighty Yahoo, coming out with promising tools then letting them die on the vine. This is not OK - they are wasting developers' time, consumers' time and their own staffs' time. So you can't argue that Google isn't at fault here.
you should NEVER rely on ANY API
Well that's a bit extreme, a better approach would be to acknowledge that your reliance on an external API is a risk that you're taking in order to save the development costs of DIY. If it's critical to your system, you need to have as part of your risk management a plan B that you can either switch to, or develop in the background. But overall trading development time for some risk makes sense a lot of the time.Unless the API is something with no alternative, and not easy to replicate, then you have an issue.