Earlier quoted context omitted.
Never explain with stupidity what can be explained with economic self interest.
"Never explain with stupidity what can be explained with economic self interest." Nasmorn's Law
Why should anyone ever use a Google API again?
131–140 of 185 posts
Re: Why should anyone ever use a Google API again?
#132Earlier quoted context omitted.
Relying on someone else's good will for the lifeblood of your company is insane Tweetdeck anyone? And Zynga (FB is its lifeblood) Google shutting down an API that thousands of developers are relying on without much warning is insane. The web is an increasingly competitive space and there are lots of walled gardens to worry about. Google openly encourages developers to build on top of and use its APIs and it prides it…
>> Tweetdeck anyone? And Zynga (FB is its lifeblood) Exceptions are not the rule.
Re: Why should anyone ever use a Google API again?
#133I keep hearing about hypothetical for-profit products and people's weekend hobby projects being affected by this change, but does anyone have any example of an actual business that will be affected by this change? Note that most of these APIs have 3 year deprecation policies and so will continue to be around; only the translate api is going away (and that's in December). I have serious doubts that almost anyone would…
Re: Why should anyone ever use a Google API again?
#134Re: Why should anyone ever use a Google API again?
#135Thanks Google! Ya dumb fvcks.
Re: Why should anyone ever use a Google API again?
#136Google has made some unpopular developer-facing moves lately (App Engine pricing changes come to mind), and it seems entirely out-of-character. From now on, any API announcement from Google should be accompanied with a GIANT expiration date stamped all over it by default. Then, if it keeps going... happy surprise!
I agree, something strange is definitely going on internally at Google. I actually attribute it to starting with the shutdown of Wave and the floundering about with Buzz and other products since then. One thing that Google has been excellent at doing is building up the perception that they have near limitless computing power at their disposal. These kinds of shutdowns, and the reasons given, are doing immense harm to…
Re: Why should anyone ever use a Google API again?
#137Earlier quoted context omitted.
There's a big difference between flicking a switch to turn off python 2, and slowly deprecating it over a period of years to a new (better) system with well doucmented differences and a clear migration path. Python 3 started in 2006 ( http://www.python.org/dev/peps/pep-3000/ ), if you've managed to stave off software rot for the last 5 years, I'm sure you can take the extra step to support python 3.
Upgrading to Python 3 is simply not an option for me at this time as I am depending on libraries that still require me to be using Python 2: Python 2->3 is an "all or nothing" endeavor due to the horrendously incompatible way they have handled this transition. I mean: the fact that five years /have/ passed and Python 3 is still a silly pipe dream for almost all users of Python should tell you something about how poor…
So far, it has been just how it was meant to be. It was never the goal for Python 3 to be the default Python version by year 2011.
Re: Why should anyone ever use a Google API again?
#138Earlier quoted context omitted.
There are billion dollar companies like NetFlix completely reliant on AWS APIs.
I would be willing to bet that most of them have mitigation strategies in place that they can, at least in part, switch to. They don't use them because they are less cost effective than AWS (or other current providers) but they should be able to switch with relatively little notice.
I don't see why NetFlix would have to be more paranoid about AWS, then say Apple about Foxconn. Business is business, except at Google.