Comment by kazinator
21 days ago
It's the forced revisionism of what "kilobyte", "megabyte" and "gigabyte", that has caused most of the confusion.
Especially that it was only partially successful.
Which is not to say that there had been zero confusion; but it was only made worse.
What forced revisionism?
Things like hard drives often used decimal/metric sizing from the start. Because their capacity has always been based on physical platter size and density, not powers of two the way memory is.
So this confusion has been with computing since the beginning. The attempt to introduce units like KiB isn't revisionism, it's an attempt at clarity around something that has always been ambiguous.
And obviously, if you need two separate prefixes, you're going to change the one whose unit of measurement differs from all the rest of science and technology.
> The attempt to introduce units like KiB isn't revisionism
Yes it is; it is literally asking people who call 1024 bytes "kilobyte" to stop doing that and say "kibibyte" instead, and to revise the meaning of "kilobyte" to 1000 bytes.
Some people have not stopped doing that, so there is more confusion now. You no longer know whether a fellow engineer is using powers of 1000 or powers of 1024 when using kilobyte, megabyte or gigabyte; it depends on whether they took the red pill or the blue pill.
It's a partial renaming but it's not revisionism.
> You no longer know whether a fellow engineer is using powers of 1000 or powers of 1024 when using kilobyte, megabyte or gigabyte
You never knew this, that's the point. You didn't know it in e.g. 1990, before KiB was introduced in 1998. People didn't only start using powers of 10 once KiB was formally introduced. They'd always used them, but conventions around powers of 10 vs 2 depended greatly on the computing context, and were frequently confusing.
There isn't more confusion now. Fortunately, places that explicitly state KiB result in less confusion because, at least in that case, you know for sure what it is.
Unfortunately, a lot of people won't get on board with it, so the confusion persists.
And frankly, I don't care what you call it when you're speaking, as long as you just use the right label in software and in tech specs.
2 replies →