Sorry, this tweet is nonsense. The implementation is in assembly because people complain about crypto performance and to avoid side channels. Code was written by competent people who should implement crypto. Language is not "safe", it's safe against some mistakes, not logic bugs.https://twitter.com/marcan42/status/946252676781748224 …
Yeah, but all of those are big libs that do lots of stuff. Among them, how many times are the same *primitives* implemented? You usually only need *two* versions: the fast one, and the comprehensible/short one. Within the fast one you need optimized assembly for N architectures.
-
-
Ah yes. Depends on where you draw the line at the protocol level. I'd say higher level bugs are more common than issues with the primitives, and so your "base library" would need a larger set of stuff.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.