https://physics.nist.gov/cuu/Units/binary.html
I'm curious how other developers define kilobytes/megabytes/etc.
1–7 of 7 posts
https://physics.nist.gov/cuu/Units/binary.html
I'm curious how other developers define kilobytes/megabytes/etc.
I think hard disk makers have been using 1000 for some time.
I personally prefer the base-2 definitions despite the fact that they do not follow metric prefix naming.
The standard metric prefixes would make more sense if 10-bit bytes were used (one byte == one decabit == 10 bits).
That begs the question: Should we have metric bytes?
Then at some point hard disk manufacturers decided to change and to use SI prefixes as well. Iirc that was when off-the-shelf HDDs reached GB scale.
This all lead to the creation of kibibytes, etc. which I think is clear and solves the confusion created by effectively using SI prefixes incorrectly.
"Traditionally", memory/storage uses kilo=1024, etc, and data transmission uses kilo=1000. So 32kB RAM means 32,768 bytes and 32 kbps means 32,000 bits per second. Then at some point hard disk manufacturers decided to change and to use SI prefixes as well. Iirc that was when off-the-shelf HDDs reached GB scale. This all lead to the creation of kibibytes, etc. which I think is clear and solves the confusion created by…