On: Git.io deprecation

[BoorishBears]

> That’s not deprecation. That’s breaking the method.

It's both. You can even break a feature and deprecate it for that reason. Deprecation comes down to communication.

> deprecation means that functionality is not materially altered from how it was before the deprecation.

No it doesn't. Maybe you really want it to, but it doesn't.

> This notice is not a deprecation, because the service was already deprecated.

That's not how that works... you can deprecate something and deprecate it again. Each notice is the deprecation if you don't realize this I don't know what you're still going on about...

[InsomniacL → BoorishBears]

> It's both. You can even break a feature and deprecate it for that reason. Deprecation comes down to communication.

To deprecate something is to recommend against it's use, but it must still be possible to use it without heeding the depreciation.

Removing all the functionality of something and replacing it with a debug message is not depreciation, it's discontinuation.

>> deprecation means that functionality is not materially altered from how it was before the deprecation.

> No it doesn't. Maybe you really want it to, but it doesn't.

Do you accept that your view of deprecation is not compatible with the definition in say, Wikipedia?

[EdwardDiego → BoorishBears]

You're very wrong about how deprecating an API works.