3 ms·
> This is flatly wrong. It's not flatly wrong, you're just stuck on a tautological use of the word "work"... after all how do you deprecate something that does
by BoorishBears 5y ago
> This is flatly wrong.
It's not flatly wrong, you're just stuck on a tautological use of the word "work"... after all how do you deprecate something that doesn't exist?
I used the example below: you can stub out a method with a print statement that says "don't use this" and still deprecate it.
The function still "works" in the most literal sense... it just doesn't do any useful work. It doesn't work.
> Semantically, that was clearly a deprecation of the service: it keeps working, but they discourage its use as it will be discontinued in the future.
You can't call the original a deprecation and say this one is not. Git.io still works (in reduced but extremely meaningful capacity... git.io links all still work) and they're recommending alternatives.
Your other hang up is said they will deprecate something during a depreciation.
That's perfectly allowed if you're actually going to be this pedantic? I will run while I'm running doesn't make it a false statement.
Also to be clear I'd just rather people not be as pedantic as the grandfather comment. Sometimes it's good to hold up a mirror to that end.
- chrismorgan 5y agoYour quibbles are altogether unreasonable. > you can stub out a method with a print statement that says "don't use this" and still deprecate it. That’s not deprecation. That’s breaking the method. To define “works” somewhat more specifically: deprecation means that functionality is not materially altered from how it was before the deprecation. (You might devise some way of notifying users—e.g. DeprecationWarning in Python, #[deprecated] in Rust—but this does not materially alter functionality.) The January notice was a deprecation (even if they mislabelled it). This notice is not a deprecation, because the service was already deprecated. This notice defines a sunset timeline, but does not alter the parameters of the deprecation.
- BoorishBears 5y ago> 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 5y ago> 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 5y agoYou're very wrong about how deprecating an API works.