> > But raffi why do you have to break the old to offer the new? >
we do our absolute best not to do so. as i mentioned in some previous thread - we do reserve the right to add things to the XML / JSON / etc. outputs -- so, please make sure to have parsers that can handle that. for me, that doesn't break our definition of "backwards compatibility". Basically I've just updated MyPostButler to work again after your last > unannounced changed the Thursday evening before a holiday break only to > open my email this morning and see you are going to modify search api > yet again in some undetermined period of time. > as a FYI, we now have a policy here on the engineering team at twitter to not deploy any code on fridays (and long weekends and the like) - hopefully this won't happen to you again. but, of course, as with any change, there is a chance for a regression. we do our best to try to make sure that things don't break, and we try to react quickly when they do. please remember that twitter is a constantly evolving platform. > I understand things need to change from time to time BUT why so often? > Why cant you make the new changes opt-in rather than breaking all the > previous applications already deployed out there. > again - its an evolving platform. we do our best to make things backwards compatible. i'm happy to provide hints on how to make sure your code can be resilient to forward changes if you want me to. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using "remove me" as the subject.
