Facebook making breaking changes does piss people off. It's interesting that it doesn't kill the apps. I can't remember any single change Facebook have made - possibly just because tere's so many - but I do remember when twitter made everyone switch to OAuth. People complained about that kill date.
Re:Don't Build APIs
by planckscnst on Wednesday April 18, 2012 @08:51PM
(#3860918)
I think developers tend to love backward-compatability while users hate it.
As a developer, it means we don't have to keep digging out the old projects and porting them to the new API.
As a user, it means we are left with systems that have many years of cruft and with features being held back from systems because they couldn't make it backward-compatabile.
I think most users are willing to pay any higher price that will result from developers being required to work harder to port their software.
Users love it when their software still works even after they've upgraded another bit of the overall system.
Re:Don't Build APIs
by anonymoushn on Wednesday April 18, 2012 @09:57PM
(#3861064)
As a developer, I would rather have my code break than continue to use a terrible API.
How about fixing your application, because your terrible API were deprecated, for an application that is quite old, bit still in support ? (and of course for free, because client don't expect to pay for a compatibility fix).
Obviously the needs for a web API and the needs for an API with a specific binary ABI on a local OS are quite different but I think for either environment, most API developers can comfortably fit somewhere between those two extremes where they don't continue to support inherently unsupported API usage, but they don't break something randomly every week.