It sounds like you're imagining open source whereas the comment you're replying to is imagining more intra-company dependencies.

▲

mbreese 39 minutes ago | parent [-]

I think deprecation in intra-company code is a completely different beast. You either have a business case for the code or not. And if something is deprecated and a downstream project needs it, it should probably have the budget to support it (or code around the deprecation).

In many ways, the decision is easier because it should be based on a business use case or budget reason.

	▲	zamadatix 12 minutes ago \| parent [-]
		The business case is the easy part, the quagmire is in getting the different teams to agree who should support the business case, why it's more important than the business cases they wanted to spend cycles on instead, and how much of the pie supporting it takes on the budget side. Less so when the place is small enough everyone knows everyone's name, more so when it's large enough they really don't care what your business case is much even though it'd be 10x easier to support from their side instead of another.