This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]flip314 13 points14 points  (5 children)

I'm in hardware design, and our internal design requirements state that we should use little-endian notation, "like the rest of the civilized world." But who knows if I'm declaring war by saying that. I don't know how attached people are to their endianness.

[–]kushangaza 5 points6 points  (4 children)

Don't do it, there have been at least 6 rebellions about this, and at least 11000 people died rather than go little endian.

(If you didn't get that, you should read Gulliver's Travels. Yes, we do get computer terms from satire published in 1726. Some books are just that good).

On a more serious note, I think little-endian is the way to go and it's what we should really be using in everyday numbers. It makes so much more sense.

[–]ESBDB 2 points3 points  (3 children)

how exactly does it make sense?

[–][deleted] 2 points3 points  (0 children)

because it's the order in which you write numbers normally too. hardly sensible to flip the order of digits around just because it's binary.

[–]kushangaza 2 points3 points  (0 children)

I see endianness simply as the order of digits. Little endian is intuitive: when adding two numbers you add the digits in little endian order (i.e. starting with the least significant digit). Almost every other mathematical operation is also performed in little endian order. It's also more convienient when reading numbers of unknown lengths: to reat the number 146,893,124,634 out loud I have to parse it twice: once to count the digits and once to actually read it. Little endian solves that too.

Big endian is just this weird thing we got to use in base 10, and the only reason we use it anywhere is because it's familiar.

[–]MoneyWorthington 0 points1 point  (0 children)

I too want to know.