Google was ok giving you a connection to translate because you were helping them build up the system. Now the most powerful database of human language is going to be locked up. We should all learn a lesson from this...
Why should anyone ever use a Google API again?
181–185 of 185 posts
Re: Why should anyone ever use a Google API again?
#182Earlier quoted context omitted.
For e.g. the translate API, how could they train their algorithms? There is no feedback associated with it (that I know of).
Static analysis of lots of human translators' output. Given the input and output of a strange human filter, they're trying to approximate the filter using machine learning. When their algorithm's output approximates the best translations, they're done.
Re: Why should anyone ever use a Google API again?
#183Earlier quoted context omitted.
Yes, and it is deprecated, not shutdown: "we have no current plans to remove existing functionality".
Fair point, but isn’t that basically what deprecation is? A communication that something will likely stop working at some point?
Re: Why should anyone ever use a Google API again?
#184Earlier quoted context omitted.
Except that they provided a replacement and a migration path.
And you could keep on using VB6. I wouldn't be surprised if there still aren't thousands of business critical apps that still aren't using it. Web Services are different in that when they're no longer supported, you can't use them.
Re: Why should anyone ever use a Google API again?
#185My guess is Google setup these APIs to help train their learning algorithms. Now that they are trained there's no reason to keep up the service anymore. Maybe the key is to stay away from APIs that do work and don't contribute to revenue?
For e.g. the translate API, how could they train their algorithms? There is no feedback associated with it (that I know of).