> just include in the warning that it is not maintained.

I'm convinced this isn't possible in practice. It doesn't matter how often you declare that something isn't maintained, the second it causes an issue with a [bigger|more important|business critical] team it suddenly needs become maintained again.

▲

tux3 4 hours ago | parent | next [-]

And here's where your business can contact me to talk about a support contract.

If it's important, they'll pay. Often you find out it wasn't that important, and they're happy to figure it out.

▲

nisegami 3 hours ago | parent [-]

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

▲

mbreese 38 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 11 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.

▲

taeric 4 hours ago | parent | prev | next [-]

I don't know that I see why/how this is a problem? You would do the same with any other thing in your life?

More, in many things, we have actively decided not to do something anymore, and also highly suggest people not mess with older things that did use it. See asbestos. Removing it from a building is not cheap and can be very dangerous.

▲

dietr1ch 3 hours ago | parent | prev [-]

It also keeps slowing down development as getting a green global compile will make you still update "deprecated" functions that face breaking API changes.