4 ms·
> we were even arguing about endianness for God's sake Why is that? Where you scared that developers might have made mistake while typing constants in their im
by baby 11y ago
> we were even arguing about endianness for God's sake
Why is that? Where you scared that developers might have made mistake while typing constants in their implementations?
- tptacek 11y agoBecause there is a little-known IETF/IRTF bylaw that no important standards debate can take place without relitigating endianness. You might think I am joking, but I am not. It's Postel's Second Law.
- AlyssaRowan 11y agoQuite! Some like big endian, because tradition ('network byte order'); little endian, because simplicity (current CPUs); mostly it's actually just classic bikeshedding¹. Since X25519 and Ed25519 had already been deployed by a fair few people, all of whom used little-endian, recommending the opposite without a compelling reason would have been a bit too silly. (Upstream working groups are encouraged to consider the field elements as opaque octet strings, to try to avoid arguing the exact same point again.) [1] http://bikeshed.com/ http://bikeshed.com/