3 ms·
It does (inevitably) really depend on the quality of the library. We really saw this for say, SSL deprecation. If you made good choices (e.g. maybe you depend
by tialaramex 6y ago
It does (inevitably) really depend on the quality of the library. We really saw this for say, SSL deprecation.
If you made good choices (e.g. maybe you depend on Python's Requests) you had to go out of your way to make problems for yourself, by default the software understands that it should prefer shiny modern cryptography, allow anything that's probably fine, and reject nasty broken stuff. What counts as "shiny modern" or "nasty broken" will vary over time, but it's not likely you, as the application developer, were best placed to decide when you wrote the code, so unless you specifically did so the runtime decides.
In contrast Microsoft shipped not one but several distinct C++ APIs and .NET APIs where you'd need to go back and periodically modify old code (e.g. to specify newer TLS versions) or now it doesn't work because there was no provision for programmers to just let the runtime do the Right Thing.