Why Larry Page Google Translate API killed and other assorted thoughts

My first post on Google's decision to close its hugely popular move was the most retweeted API and the most ever read GTS blog. I should also mention that I started a discussion on Linkedin, which received comments on some very important people in the industry as Alon Lavie MT, Manuel and Jeff Allen Heranz. It's worth checking out.
Now that the dust begins to settle, here are some more thoughts on this topic.

•     Translate API is not the only language API obsolete. Google depracated his family API language. This includes Transliterate, keyboard and Diacrtitize.

•     To finish off the move the API must have come from the top: CEO of Google, Larry Page. Because the page took on the duties of the Director-General Eric Schmidt about a month ago, reports are that it is much more focused on products and technologies. I'm guessing that Larry does not believe that the translation of the API is a part of this focus.

•     Google Translate API is closed because of the economic burden caused by the widespread abuse. How serious was the economic burden? No one can say for sure (and Google keeps quiet about it), but I have a few theories. The consensus seems that the API is used to translate the mass transfer of Web sites to manipulate the SEO. If this is true, all over the world the Internet has become a lot more space. This means that Google needs to crawl and index many more pages than ever before. This not only means more room for storage, but would also lead to slower response times for queries. Not to mention the number of Google servers must be maintained on the ground all of these transfer requests.

•     The extensive abuse. People grossly abusing the generosity of Google and not even giving them credit for it. I mean the companies do not put "Powered in Google" in their applications, not link to Google. But it was even worse. Company accepts transfers from Google for free and charging money for it. We have a term for it in Yiddish: it is called, being «chazer.»

•     Preempting competition. It's no secret that Google is competing with Facebook in the online advertising space. Google Android also competes with some of the other smartphones on the market. By providing free translation API, Google allows third party developers to make applications for the transfer of competitive products. It really does not make sense for Google, if you think about it. Why give the competition the edge? Abolishing the transfer API, Google can take control and the best translation software for their own use.

•     Big LSP is not stupid. SDL bought Weaver language last year. Lionbridge has entered into an agreement with IBM (Geofluent). These companies will restore the dominance in the segment of MT where he belongs in the first place. Leadership in technology transfer should be retained translation companies, not by the search engine.

•     Google translator is not only a free translation of the API. Apertium, Ta with you and Microsoft offer free translator interface API. But if there is something that Google has an API completion of the transfer has taught us, it does not plan to build a product around a free API, which can not be free or may even have gone in the near future.

•     This Toolkit API Google translate next? In GTT API is currently limited, and Google says it has no plans to remove it. Does this sound met?