In fact, I've got a 20MB SCSI drive here which I should hook up to verify...
In fact, I've got a 20MB SCSI drive here which I should hook up to verify...
The real questions are: Why did hard drive manufactures move from a (misnamed) base 2 to base 10? They were confused before but then saw the light (decades later)? Why did all OSes and utilities use base 2? Why do most still use base 2? Why can't we use base 2 now?
Making the consumer think he gets more for his money doesn't give you an advantage over your competitor (if he's doing the same thing), but it does put more money into the industry as a whole. Imagine a home ice cream machine fad. All manufacturers might rise more or less equally, but they all make more money now that people believe their lives are better enhanced by putting their money into ice cream.
I think it makes sense that this didn't become significant until disk sizes started reaching GB levels, and therefore manufacturers' choices to switch to base 10.
Except when they do. Amazon Web Services uses 2^30-byte GBs for bandwidth and EBS disk sizes. They measure EC2 ephemeral disk sizes in 10^9-byte GBs, though...
I agree, but it's an error which saves us money, so I'm not going to complain too loudly... ;-)
A similar question is - why do all gas stations sell gas for x.yy9? It's impossible to sell something for 9/10 of a penny but in the U.S. they all do it.
If you ask the people doing it, you'll get the answer that it serves the consumer better, it's just a coincidence that it happens to make their product look artificially better/cheaper/whatever than it is.
Ditto with flash devices; due to their addressing architecture, they are inherently binarily-capacitised(?) I have here a 16MB USB drive from when they first came out, and it stores exactly 16,777,216 bytes, or 8,388,608 512-byte sectors. Back then, flash memory was all SLC and it was reliable enough that only the few spare bytes on each page were needed for remapping/ECC and the OS's filesystem bad-block management could be used.