Re:Twitter’s poor API documentation practices
by jlogsdon on Monday January 09, 2012 @05:53PM
(#3444708)
Facebook's API is notoriously bad, and they love to update it with breaking changes all the time without any notification or change to the documentation. It was a great day when I stopped working with it.
Re:Twitter’s poor API documentation practices
by ovechtrick on Tuesday January 10, 2012 @07:55AM
(#3446764)
I'm pretty sure several of my gray hairs can be attributed to the facebook API.
Re:Twitter’s poor API documentation practices
by matwood on Tuesday January 10, 2012 @09:44AM
(#3447069)
I wonder if FB (and Google for that matter) are starting to suffer from their hiring that slants towards young recent college grads. All the cool kids only want to work on and build new things. Fixing bugs, cleaning code up, making it professional, etc... is for someone else to do. The problem is that 'someone else' doesn't really exist in those companies.
Re:Twitter’s poor API documentation practices
by bkaid on Monday January 09, 2012 @06:03PM
(#3444746)
Facebook API had so many breaking changes happening all the time that they decided, as a "benefit" to developers, that they would stack them all up to occur on the first of each month. This is in the name of BS called "operation developer love". And this is only for the breaking changes that get announced. The much more common scenario that ComputerGuru mentions is where stuff gets broken, acknowledged as a bug Facebook, and then never fixed. If you read the stats they publish in their blog posts, 2-3x the number of bugs get accepted than the number that get fixed, EVERY SINGLE week.
Re:Twitter’s poor API documentation practices
by FuzzyDunlop on Monday January 09, 2012 @07:13PM
(#3444990)
I read this and I think, why would I even want to write code for an API that I'd have to maintain far more actively than the rest of my project?
They've even faffed with the basic generated widgets enough for you to have to keep an eye on what works, so you can prepare to fill the same form in yet again to get the same thing working again.
Stability should be the priority if you don't want to piss third party devs off.
Re:Twitter’s poor API documentation practices
by kingofspain on Monday January 09, 2012 @07:18PM
(#3445010)
Ugh. I did a favour for someone by added some very basic FB integration to his site. I've had to go back 2 or 3 times to fix it and he now thinks I'm pretty incompetent as a result.
For instance, Facebook. For months now, the Like button has been completely broken on any sites that classify themselves as og:type product. Which is basically, very many indeed.
The bug? Some idiot at Facebook apparently registered type "product" as belonging to a particular app id. Now no one other than this unknown entity is allowed to use og:type product.
The problem is, it could be easily argued that the single-most feature of the facebook API is the like button. If the very core of their "business" is so overwhelmingly neglected and broken from an API perspective, how can anyone trust them to do anything right after that? How can anyone feel comfortable building on the Facebook platform, basing the existence of entire products, startups, and companies on the whim of such a ridiculously unorganized company and their broken API?
The age of web apps is great, but you cannot blame anyone for lamenting the end of an era where your products were as good as your code - not reliant on the whims and caprices of a company that you can't trust to maintain their API - or even build it right in the first place.
https://developers.facebook.com/bugs/285421101492706?browse=...
Facebook has 'acknowledged' the issue, but what's the use of that?