While that’s technically correct, it does not reflect common (or historical) usage, and IMHO would cause more confusion than the current phrasing. In the past 15 years, I’ve discussed bits, bytes, nibbles, and obscure mainframe gubbins, but I have never heard “MibiByte” or “GibiByte” in spoken conversation.
Can you even say “MibiByte” with a straight face? I can’t.
posted from my MacBook with 2 GibiBytes of RAM running Mac OS Ten Ten point Five point Eight.
Yes, that is a good start, but until harddrive manufacturers start using the correct SI-prefixes and not the prefix that gives them the highest number users will still complain about that the OS don’t detect the full size of the harddrive…
But it would still be good to state the correct SI format when it accually is stated as accual
It can hardly be more confusing to use the correct SI-format than using two different defenitions for the same acronym in the same sentence…
Yeah, I’m advocating that all OSes should allow display of both.
I recently realized that my TiVo’s web interface calculates GB in decimal (ie, 1 GB = 1 billion bytes), which made me paranoid when I was downloading files because a 7.16 GB file (according to TiVo) downloaded as a 6.51 GB (according to Windows)… I restarted a download that was actually complete before I realized why there was a discrepancy.
Yes, I definitely would like consistency, even if it’s wrong…
its probably as hard disks continue to grow, and the difference between decimal and binary grows ever larger, and users care less and less about the underlying storage mechanism, it would probably be simplest if everything and everyone counted in decimal (as snow leopard now does)
Unfortunately, you have that backwards. The SI prefixes require kilo to mean 1000 and not 1024, and mega to mean 1,000,000 and not 1,048,576, etc. See http://en.wikipedia.org/wiki/Kilobyte, as well as http://www.bipm.org/utils/en/pdf/si-brochure.pdf, page 103, marginal note, which states “These SI preﬁxes refer strictly to powers of 10. They should not be used to indicate powers of 2 (for example, one kilobit represents 1000 bits and not 1024 bits).”
Therefore, the hard-drive manufacturers are already using the correct SI prefixes.
Dobo Dashboard says that I have 1.5 TB + 1.5 TB + 500 GB + 500 GB = 4.0 TB (3.63 TB Actual*). You have a * indicating that there should be an explanation somewhere (not that I could find it). Since the drobo software explicitly uses BOTH units with the SAME prefix, I have NO IDEA which unit is used in the graph bellow. This is bad UI design and somewhat confusing.
It seems like it would be incridbly simple to tweak the strings in the dashboard UI to say 1.5 TB + 1.5 TB + 500 GB + 500 GB = 4.0 TB (3.63 TiB*) and if necessary switch the reported unit in the graph bellow. To further clean up the UI, I would detect the unit used by the underlying OS (Snow Leopard, Linux: SI unit. Everything else: binary unit) and display that on the graph bellow. And for a bit of polish I’d render the graph just like iTunes.