3 ms·
That’s a pretty nice set of steps, a genuine deprecation including even as good an attempt as is possible at notifying where it’s needed, rather than just a rem
by chrismorgan 5y ago
That’s a pretty nice set of steps, a genuine deprecation including even as good an attempt as is possible at notifying where it’s needed, rather than just a removal. It’s interesting to note that they don’t say when they’ll finally remove it.
(One of my pet peeves is people abusing the word “deprecate” when they mean “remove”. The word “deprecate” means just discouraging something without actually removing it, though it’s typically a precursor to subsequent removal.)
- iudqnolq 5y ago> It’s interesting to note that they don’t say when they’ll finally remove it. It's right at the start of the detailed timeline section: "While we will enforce a minimum of TLS 1.2 beginning October 4, 2021, we will also take steps to alert affected users to this change ahead of the deprecation."
- kevincox 5y agoIt is a bit odd that it isn't in the timeline though. I also got to the end of the timeline and though for a second "what about the full disable" before reading the start of the article again and finding it.
- chrismorgan 5y agoFailing to notice that (twice, even, apparently!) was surprisingly careless of me. Thanks for the correction. But yeah, I do think it would be significantly better restructured to put that at the end of the bullet list. … actually, reading this all more carefully now, I retract my praise of this as “a genuine deprecation”. They’ve abused the word deprecation like so many others. I fear the word will soon be lost to us, as more and more people misuse it. “This year, we will similarly deprecate non-HTTPS access and TLS 1.0 and TLS 1.1 for npmjs.com, the public npm registry.” No, you will similarly remove it. “we will also take steps to alert affected users to this change ahead of the deprecation.” — no, you’ve deprecated it now, and are taking steps to alert users ahead of the removal. “The npm registry is removing TLS 1.0 and TLS 1.1 support” would have been a more accurate title.
- iudqnolq 5y agoI agree it's strange
- nerdponx 5y agoRight. It is now currently deprecated as a result of this announcement. It will then be removed according to the schedule in the announcement. Super confusing because they do not mean the same thing and I can't imagine why anyone would think they do.
- kens 5y agoYes, misusing "deprecate" as a synonym for "remove" is a pet peeve of mine too, since the meaning is completely different. (There were a few word usages at Google that always annoyed me; "deprecate" was one, along with using LDAP as a synonym for "user id" and "turn down" for "shut off".)
- millerm 5y agoMy 82 y/o dad still “warms up” his computer.
- kens 5y agoSince some people might not know the history here, back in the vacuum tube days, you needed to let something like a TV warm up for a few minutes before it would work. Vacuum tubes contain a filament (much like the one in a light bulb) and it needed to heat up the cathode before the tube would start working. Later, manufacturers introduced "instant on" TVs that would keep the filaments powered even when the set was "off". This wasted electricity but you didn't need to wait for the tubes to warm up.
- globular-toast 5y agoI didn't realise this was a problem until recently. We decided to deprecate a feature and an engineer immediately submitted a merge request to remove it. I asked wtf they were doing and they said they didn't know the difference. All this time I've thought everyone understood but now I see misuses everywhere and need to clarify all the time.