caterpillarcowboy: mcdavis: Random Programming Notes: This is a screenshot from Firebug’s timer for AJAX calls.  Each call is calling an internal PHP page that pulls an API from one of three different services (Facebook, Twitter and Tumblr).  Notice two are almost identical in response time (this happens nearly every time).   The one call that is different of the three (responding over 9 seconds after the call is originally made) is Tumblr. I’m glad Tumblr has an API at all, but it’s really quite lackluster. I know they could do better if they wanted to. Which brings up an interesting point: when you introduce an API, you are deciding to create a second type of customer - the developer. And that customer should be treated with equal respect as any other customer, even if there are fewer of them. Too often companies will release an API because they can or because they should, and then leave it to rot. If you’re going to do it, do it all the way.
View Separately

caterpillarcowboy:

mcdavis:

Random Programming Notes: This is a screenshot from Firebug’s timer for AJAX calls.  Each call is calling an internal PHP page that pulls an API from one of three different services (Facebook, Twitter and Tumblr).  Notice two are almost identical in response time (this happens nearly every time).  

The one call that is different of the three (responding over 9 seconds after the call is originally made) is Tumblr.

I’m glad Tumblr has an API at all, but it’s really quite lackluster. I know they could do better if they wanted to. Which brings up an interesting point: when you introduce an API, you are deciding to create a second type of customer - the developer. And that customer should be treated with equal respect as any other customer, even if there are fewer of them. Too often companies will release an API because they can or because they should, and then leave it to rot. If you’re going to do it, do it all the way.

Source: mcdavis

Recent comments

Blog comments powered by Disqus