3 ms·
>> and CurvePreferences to avoid unoptimized curves The key word being unoptimized. In the article, the code snippet has a comment "Only use curves which have
by edmccard 10y ago
>> and CurvePreferences to avoid unoptimized curves
The key word being unoptimized. In the article, the code snippet has a comment "Only use curves which have assembly implementations" and he mentions that "a client using CurveP384 would cause up to a second of CPU to be consumed on our machines." (presumably because it does not have an assembly implementation)
> Programmers should not need to know this stuff.
It can sometimes be a sign of a leaky abstraction, but programmers might need to know the performance characteristics of the code they write.
- smegel 10y ago> Only use curves There you go again. Programmers should not be "using curves". It's idiotic to think the average programmer can make that kind of decision. And it's so very typical of the arrogant fools who develop certain software to expect or assume developers would or should know this stuff, and if they don't they shouldn't be writing software or such.
- sctb 10y agoPlease stop breaking the guidelines. They ask us not to call names like this because it's not conducive to having the types of civil discussions that this site is for. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- 4ad 10y ago> Please stop breaking the guidelines. How about you stop breaking the guidelines? The parent didn't break any guideline.