3 ms·
> After thinking this through, however, I realized that one of the largest mistakes an API company can make is to remove previously advertised functionality (wh
by derefr 14y ago
> After thinking this through, however, I realized that one of the largest mistakes an API company can make is to remove previously advertised functionality (why would developers trust you to provide data to them if you're so quick to remove functionality?).
It seems to me that when providing a new feature in your API, you should have a latency period at the beginning where it is not guaranteed to continue to exist. Sort of the dual to the deprecation period at the end-of-life of a feature (would this make it an "imprecation period"?)
After that period passes, that's a signal to your API consumers that the feature will definitely be sticking around and receive long-term support. But until then, it could be removed without warning at any time; all code that relies on it should have alternate branches to handle the case where the feature endpoints pop out of existence.
Pre-1.0, all features are implicitly imprecatory, of course.