[bkaid]

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.

[FuzzyDunlop]

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.

[kingofspain]

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.

[lrobb]

My favorites were bugs filed where numerous people would post about it, fb would never respond, then after a few months they would just "close" it due to inactivity!

Mind-boggling.