I can't help but imagine all the good Google could have done if it had done this go Wave (either by pivoting it into a better product, or by leaping the whole team into greener fields sooner).
A personal qualification: I may be unusual, but my personal concern (as opposed to professional needs) is use by tools such as the Firefox Babelfish extension.
At times, I spend significant time in communities speaking any number of languages. Being able to drag-to-translate various items, pretty much instantaneously (and without forcing the entire page through a single translation), makes participation fluid. It also props up my sometimes dormant, if not non-existent, understanding of those languages.
I hope there is room within the new model to support this, at reasonable cost, whether through being simultaneously signed in to a Google account (hopefully with adequate security filtering for the submitted fragments), or other means.
I can't help thinking there's also an educational aspect to similar scenarios. Always good for a little PR!
P.S. As long as I'm asking, how about HTTPS support?
In this light, seeing Google actively driving commercial sense into their services and cancelling those that will never fly is, while disappointing, also reassuring.
Granted, they support a lot less languages, but for the supported ones, MyGengo sounds like a much better option, unless Google manages to improve their translation and beat MyGengo pricing.
The quality of the Google Translate is awesome, considering it's automatic, but still falls short of the human doing the job. Also, it'll be interesting to see what Duolingo (http://duolingo.com/) can do, once it launches.
As far as I know, MyGengo doesn't do in house manchine translations. Am I wrong?
You can also get free machine translation through our API - so no need to switch between services. Just pick and choose which of your content you want done by humans, and which by machines. It’s easy and free to start with machine translation, and then upgrade for popular content.
We currently source our API's machine translation from Google, but we're going to be connecting to several other providers in the next few months. Depending on Google's pricing model we may or may not include them in the roster.
We think it's best to connect to our API, because you can 'upgrade' to human translation without switching out code (it's just a single parameter in an API call).
If you want to try us out, we're currently running a $25-credits-free campaign to switch to our API.
That is, in sufficiently large consumer bases, is it safe to rely on shitstorms for negative feedback on business decisions?
Some groups have outspoken representatives that can get the word out there so that it can snowball into something that can be noticed.
However, what if the average emotional response to the decision had been the same, but no shitstorm was raised? Does it happen often? In what conditions?
We offer machine translations for free, but also offer human translations for (IMO) pretty good rates, and they can all be gotten from the API. I assume the parent comment (of the parent comment of this comment... yeah) was speculating on how we were planning to deal with Google ever deprecating their machine translation. :)
tl;dr I don't believe we were ever too worried, as we're certainly no slouches in the tech department ourselves. Initial shock was there though, definitely a "wtf" moment.
Also see comment above, about machine translation support at mygengo.
P.S. And by the way I tried not to use the google api (well before the announcement) and wrote a basic word by word translation which obviously gives dismal results (https://github.com/aparij/bl)
Microsoft Ad center was also a walk in the park compared to Google Adsense. I am a novice though.
The new layer is data locked into private site that farm content.
you do have to consider many of those searches as looking for stuff already in their social graph (friends, pages, etc). i know i use their search to navigate all the time.
Obviously at this point it is largely just offsetting personal email, but I don't think it's reasonable to dismiss that as insignificant.