Re:Modern Alternatives to PGP
by tedunangst on Friday February 15, 2019 @05:05PM
(#19175145)
How is it possible for so many people to read the words "not remove" as "remove entirely"?
Re:Modern Alternatives to PGP
by MrStonedOne on Saturday February 16, 2019 @12:05AM
(#19177174)
deprecate is assumed to be followed by removal, doing one will lead to the other 99% of the time.
Systems exist outside of the Go ecosystem and not all systems are new. Compatibility is important. It's great to flag these as not recommend for new designs, but it's quite another to remove them entirely and prevent people from easily implementing compatible software. Seems more like something that should be in the documentation or spit a compiler warning if that isn't deemed loud enough.
MD5 is similarly broken but I'm assuming they don't want to remove it because it's still quite popular in some use cases - what exactly is their standard for that popularity?