It's sad that the first use case I see for this is API documentation. Why do so many firms, even in a B2B space, love the flow of "We introduced Shiny New API

It's sad that the first use case I see for this is API documentation. Why do so many firms, even in a B2B space, love the flow of "We introduced Shiny New API 3.0, gotta shred every reference to Boring old API 1.0!". Or even "A and B merged, and we're going to eliminate any reference of B's APIs". I can see "we'll move the content to /legacy and link it at the bottom of the page", but someone must be saying "you know, we still have actual customers paying money for these services, and they may have bugfix/compliance/feature update needs that justify leaving the docs around." I suspect there are some services where the ONLY documentation that exists are the copies my firm retained from the original late-2000s/early-2010s integration.