For all its boasting about doing what's right for developers and sticking with them, when subtly comparing Google+ to Twitter, Google doesn't have such a great record when it comes to API support. Granted, it still does better than most, but it also kills off APIs that no longer favor it.
The latest example, albeit not a particularly damning one, is the Weather API. You'll be forgiven if you didn't know that Google had a weather API because, for one, it has a long, long list of APIs, and, two, because the API is private. Even so, it was being used in the wild.
But Google seems to have quietly
disabled the API as Google's own Status Dashboard shows. Developers that were relying on it are already switching to other similar APIs.
At least, in this case, they're fortunate enough to have an alternative, unlike the Translate API which Google wanted to kill leading to quite the backlash. In the end, Google decided to start charging for the Translate API.