End Of Life Procedures
From APIDesign
(Difference between revisions)
(New page: This section is good, and reminiscent of (symmetric to?) your section at the beginning of Part 3, "An API Must ...". One thing I would recommend: an additional section of this chapter abo...) |
(→Have You Ever Wondered...?) |
||
(4 intermediate revisions not shown.) | |||
Line 1: | Line 1: | ||
- | + | == [[Have You Ever Wondered]]...? == | |
- | + | Is it not true, that by keeping compatibility we grow the number of APIs we have to maintain? For how long can this be sustained? Will not we all spend our lives maintaining old APIs instead of developing new functionality? Not necessarily. If you know how to use end of life procedures as described in [[End Of Life Procedures|Chapter 19]], you can send you old APIs to [[black hole]] smoothly while keeping [[BackwardCompatibility]]. | |
- | + | ||
- | + |
Current revision
Have You Ever Wondered...?
Is it not true, that by keeping compatibility we grow the number of APIs we have to maintain? For how long can this be sustained? Will not we all spend our lives maintaining old APIs instead of developing new functionality? Not necessarily. If you know how to use end of life procedures as described in Chapter 19, you can send you old APIs to black hole smoothly while keeping BackwardCompatibility.