PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Tony Foiani
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"David" == David Schwartz <[email protected]> writes:
Just last night I formatted some new "500GB" drives, and they eventually came back with 465GB as the displayed capacity. Wouldn't it make more sense to display that as "465GiB"?
[...]
Quoted 5 lines
David> Adopting IEC 60027-2 just replaces a set of well-understood David> problems with all new problems.
Which are clearly solved in the standards document, and remove any ambiguity. Is one extra character really that painful to you?
If it's done in order to make disk vendors look good in spite of advertizing more than they deliver, yes.
1) This change isn't nescensary - any sane person will know that it's not a SI unit. You wouldn't talk about megabananas == 1000000 bananas and expect to be taken seriously.
2) No sane person would say kibibyte as required by the standard. You'd need a sppech defect in order to do this, and a mental defect in order to try. So why should anybody adhere to the rest of this bullshit?
Signature · 4 lines
"Whoever said the pen is mightier than the sword obviously never encountered automatic weapons." -Gen. Douglas MacArthur Friß, Spammer: [email protected] [email protected]
#include <hallo.h>
Quoted 15 lines · Bodo Eggert
Quoted 5 lines · Tony Foiani
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"David" == David Schwartz <[email protected]> writes:
Just last night I formatted some new "500GB" drives, and they eventually came back with 465GB as the displayed capacity. Wouldn't it make more sense to display that as "465GiB"?
[...]
Quoted 5 lines
David> Adopting IEC 60027-2 just replaces a set of well-understood David> problems with all new problems.
Which are clearly solved in the standards document, and remove any ambiguity. Is one extra character really that painful to you?
Quoted 6 lines
If it's done in order to make disk vendors look good in spite of advertizing more than they deliver, yes.
1) This change isn't nescensary - any sane person will know that it's not a SI unit. You wouldn't talk about megabananas == 1000000 bananas and expect to be taken seriously.
And I cannot seriosly believe that you are cappable of reading his examples. Megabananas are a ridiculous demonstration becase of the object beeing counted itself, but if you take stuff from real life then I doubt that you expect a kilometer to be 1024 meters. Same for kilogram. And a megatone is not 1048576 tones, even not 104857600 kg, and not 107374182400 grams. Wanna more stupid examples created by abusing decimal units?
Quoted 3 lines
2) No sane person would say kibibyte as required by the standard. You'd need a sppech defect in order to do this, and a mental defect in order to try. So why should anybody adhere to the rest of this bullshit?
You talk for everybody, or is it just your (and only your) mind refusing to accept new terms? For my taste, kib and mib are even easier to speech, easier than {KiLoBytE} resp. {MeGaBytE} or KaaaBe / eMmmBe.
Eduard.
Signature · 3 lines
Das Geheimnis der kleinsten natürlichen Freude geht über die Vernunft hinaus. -- Luc de Clapiers Vauvenargues
Quoted 7 lines · Eduard Bloch
Quoted 3 lines · Bodo Eggert
2) No sane person would say kibibyte as required by the standard. You'd need a sppech defect in order to do this, and a mental defect in order to try. So why should anybody adhere to the rest of this bullshit?
You talk for everybody, or is it just your (and only your) mind refusing to accept new terms?
I'd say it is the refusal to accept new *dumb* terms.
Signature · 3 lines
Stefan Richter -=====-=-=== ---= =-=-= http://arcgraph.de/sr/
Quoted 7 lines · Eduard Bloch
And I cannot seriosly believe that you are cappable of reading his examples. Megabananas are a ridiculous demonstration becase of the object beeing counted itself, but if you take stuff from real life then I doubt that you expect a kilometer to be 1024 meters. Same for kilogram. And a megatone is not 1048576 tones, even not 104857600 kg, and not 107374182400 grams. Wanna more stupid examples created by abusing decimal units?
The computer world has a long history of borrowing and abusing terms. Probably the majority of computer terms came to be that way. Why should we change any of them now? Should we stop calling it booting because some people might be confused and think it means kicking the computer? Should we rename threads because people might think it has something to do with sewing stuff together?
Quoted 3 lines
You talk for everybody, or is it just your (and only your) mind refusing to accept new terms? For my taste, kib and mib are even easier to speech, easier than {KiLoBytE} resp. {MeGaBytE} or KaaaBe / eMmmBe.
There is too much legacy code and systems around for it to ever be nonambiguous. It is too late to fix it, and the units that this "standard" came up with just sound too stupid to be taken seriously.
You also don't pronounce units just because it looks like you can. So KiB is not easier than KB. Heck most people in speach wouild just call them Ks (kays or something like that). And MBs just become Megs. Same for Gigs.
Whoever wasted their time coming up with this standard, well they simply wasted their time. It will NEVER catch on, and it will never replace the common usage. It's about 50 or 60 years to late for that.
--
Len Sorensen
Quoted 8 lines · Lennart Sorensen
Quoted 4 lines
You talk for everybody, or is it just your (and only your) mind refusing to accept new terms? For my taste, kib and mib are even easier to speech, easier than {KiLoBytE} resp. {MeGaBytE} or KaaaBe / eMmmBe.
There is too much legacy code and systems around for it to ever be nonambiguous. It is too late to fix it, and the units that this "standard" came up with just sound too stupid to be taken seriously.
For "F"s sake, when you gotta use abbreviations, then just use k=1000 and K=1024 already, b for bits and B for bytes. Problem gone.
Quoted 3 lines
You also don't pronounce units just because it looks like you can. So KiB is not easier than KB. Heck most people in speach wouild just call them Ks (kays or something like that). And MBs just become Megs. Same
kegs perhaps? :)
-`J'
Quoted 2 lines
For "F"s sake, when you gotta use abbreviations, then just use k=1000 and K=1024 already, b for bits and B for bytes. Problem gone.
K is Kelvin, k is kilo-
See ISO 31. There is a standard for this stuff which is used worldwide and only bits of the computing industry appear incapable of following it.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Jan" == Jan Engelhardt <[email protected]> writes:
Jan> For "F"s sake, when you gotta use abbreviations, then just use Jan> k=1000 and K=1024 already, b for bits and B for bytes. Problem Jan> gone.
The one-letter abbreviations are identical to SI prefixes, except for "K", which is used interchangeably with "k" (in SI, "K" stands for the kelvin, and only "k" stands for 1,000).
[...]
BIPM (which maintains SI) expressly prohibits the binary prefix usage, and recommends the use of the IEC prefixes as an alternative (computing units are not included in SI).
Some have suggested that "k" be used for 1,000, and "K" for 1,024, but this cannot be extended to the higher order prefixes and has never been widely recognised.
-- http://en.wikipedia.org/wiki/Binary_prefix
So if you continue insisting that "MB" is really 2^20 bytes, you're flouting the SI in at least two ways. I'd expect that from an USAian, not a German. ;-> (To be clear, I *am* a USAian, and I really desperately wish this country were metric...)
Some other gems from that article that haven't been covered in this thread:
* CD-Rs are generally specified in MiB, but DVD-Rs in GB
* CPU clocks are given in decimal
(See http://en.wikipedia.org/wiki/Binary_prefix#Usage_notes )
It also points out that there are some ongoing lawsuits on exactly this topic, completely analogous to the CRT diagonal cases.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Alan" == Alan Cox <[email protected]> writes:
Alan> K is Kelvin, k is kilo-
One nice thing about IEC 60027-2 is that it seems to have fixed the capitalization inconsistency; kibi- really is "Ki".
(I never cared for the lower-case "k" for "kilo-"; there are other clashes of symbols in the SI system proper; think "milli-" and "meter".)
The standard also specifically states that "B", when used with the binary prefixes, is "byte" not "Bel". Which is nice.
t.
Quoted 16 lines · Tony Foiani
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Jan" == Jan Engelhardt <[email protected]> writes:
Jan> For "F"s sake, when you gotta use abbreviations, then just use Jan> k=1000 and K=1024 already, b for bits and B for bytes. Problem Jan> gone.
The one-letter abbreviations are identical to SI prefixes, except for "K", which is used interchangeably with "k" (in SI, "K" stands for the kelvin, and only "k" stands for 1,000).
[...]
BIPM (which maintains SI) expressly prohibits the binary prefix usage, and recommends the use of the IEC prefixes as an alternative (computing units are not included in SI).
Quoted 7 lines
Some have suggested that "k" be used for 1,000, and "K" for 1,024, but this cannot be extended to the higher order prefixes and has never been widely recognised.
-- http://en.wikipedia.org/wiki/Binary_prefixSo if you continue insisting that "MB" is really 2^20 bytes, you're flouting the SI in at least two ways.
The use of SI is not even accepted on bytes.
See <URL:http://www.bipm.org/utils/common/pdf/si_brochure_8_en.pdf>.
Therefore "MB" is undefined in the SI world, and 2^20 B in the IT world.
Quoted 3 lines
I'd expect that from an USAian,
not a German. ;-> (To be clear, I *am* a USAian, and I really desperately wish this country were metric...)
I'd even prefer decimal hours, minutes and seconds.
Quoted 5 lines
Some other gems from that article that haven't been covered in this thread:
* CD-Rs are generally specified in MiB, but DVD-Rs in GB
* CPU clocks are given in decimal
Hz is a supplementary SI unit.
Signature · 3 lines
"Those who would give up essential liberty, to purchase a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin, Historical Review of Pennsylvania, 1759
Quoted 1 line · Alan
K is Kelvin, k is kilo-
K is a unit is Kelvin, k/K as a prefix is kilo.
Quoted 2 lines
See ISO 31. There is a standard for this stuff which is used worldwide and only bits of the computing industry appear incapable of following it.
--
Len Sorensen
Quoted 10 lines · Lennart Sorensen
Quoted 1 line · Alan
K is Kelvin, k is kilo-
K is a unit is Kelvin, k/K as a prefix is kilo.
Quoted 2 lines
See ISO 31. There is a standard for this stuff which is used worldwide and only bits of the computing industry appear incapable of following it.
--
Len Sorensen
Perhaps. However, in the days of kilomegacycles (KMC), micromicrofarads (MMFD), and megohms (MEG), few misunderstood what was being read. Now, with the international symbols (http://www.bipm.org/si/si_brochure/)
many seem downright confounded because it has turned out be be more politics than engineering. I well remember an early chart being published with cycles-per-second as the ordinate and hertz as the abscissa.
There are now "advertising units" where a gigabyte is something greater than what's really on the drive, where power consumption, clock speeds, transfer rates, acoustic noise, and other technical specifications do not have any basis in reality.
It is probably caused by the relegation of computers to "consumer goods." Such goods brought out such hype as IHF audio power ratings, and EPA mileage, which have nothing whatsoever to do with reality. It's not just the specs. In the United States, check out your telephone bill. What is supposed to be a US$29.95 service, bills out at nearly US$40.00. "There are lies --and damned lies..."
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.59 BogoMips). New book: http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
Quoted 2 lines · Jan Engelhardt
For "F"s sake, when you gotta use abbreviations, then just use k=1000 and K=1024 already, b for bits and B for bytes. Problem gone.
And for 10^6 vs 2^20?
Quoted 1 line
kegs perhaps? :)
Hmm, Mega -> Megs, Kilo -> Kils?
--
Len Sorensen
Quoted 6 lines · Lennart Sorensen
Quoted 2 lines · Jan Engelhardt
For "F"s sake, when you gotta use abbreviations, then just use k=1000 and K=1024 already, b for bits and B for bytes. Problem gone.
And for 10^6 vs 2^20?
"My harddisk is a 251 gB" actually even though it is advertised as 250 GB.
-`J'
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"BE" == Bodo Eggert <[email protected]> writes:
BE> 1) This change isn't nescensary - any sane person will know that BE> it's not a SI unit. You wouldn't talk about megabananas == 1000000 BE> bananas and expect to be taken seriously.
What about megaparsec? I have also seen graphs delimited in megayears. Millibar, that's another one. Not that I would have any problems talking about megabananas, if I ever had to deal with that many bananas.
/Benny
Quoted 3 lines · Bodo Eggert
1) This change isn't nescensary - any sane person will know that it's not a SI unit. You wouldn't talk about megabananas == 1000000 bananas and expect to be taken seriously.
I've met quite a few non-sane persons then. I find using kilo, mega and giga prefixes convenient to use. For example, I often use GEUR to refer to Giga Euros, because the word billion is overloaded.
Quoted 3 lines
2) No sane person would say kibibyte as required by the standard. You'd need a sppech defect in order to do this, and a mental defect in order to try. So why should anybody adhere to the rest of this bullshit?
I think I'm not sane then. I find it easy to use and pronounce.
IEC 60027-2 is a great standard! It removes some annoying ambiquity in speech and text. Adhering strictly to proper SI units (k, M, G, ...) makes life easier as they are taught in school to everyone.
Signature · 3 lines
Heikki Orsila Barbie's law: [email protected] "Math is hard, let's go shopping!" http://www.iki.fi/shd
Quoted 10 lines · Heikki Orsila
Quoted 4 lines
2) No sane person would say kibibyte as required by the standard. You'd need a sppech defect in order to do this, and a mental defect in order to try. So why should anybody adhere to the rest of this bullshit?
I think I'm not sane then. I find it easy to use and pronounce.
IEC 60027-2 is a great standard! It removes some annoying ambiquity in speech and text. Adhering strictly to proper SI units (k, M, G, ...) makes life easier as they are taught in school to everyone.
Bleh. Except for storage, base 1024 was used for almost everything I remember. 4 MB memory meant 4096 KB, and that's still the case today. Most likely the same for transfer rates.
It's just that storage vendors broke the computer rule and went with 1000. Just teach all the exceptions. No life is without.
-`J'
Quoted 3 lines · Jan Engelhardt
Bleh. Except for storage, base 1024 was used for almost everything I remember. 4 MB memory meant 4096 KB, and that's still the case today. Most likely the same for transfer rates.
Nope, transfer rates were initially 1000-based: 9.6 kbps = 9600 bps, 28.8 kbps = 28800 bps, 64 kbps = 64000 bps. Then it went 128, 256, 512 kbps = 512000 bps and 1 Mbps = 2 * 512 kbps = 1024000 bps.
But it's limited mostly to serial interfaces. Other networks use 10, 1000 etc. because they have nothing natural in (powers of) 2 so 1 Mbps may be 1000000 bps as well.
Quoted 1 line
It's just that storage vendors broke the computer rule and went with 1000.
1024 etc. is (should be) natural to disks because the sector size is 512 B, 2048 B or something like that.
Signature · 1 line
Krzysztof Halasa
Quoted 9 lines · Krzysztof Halasa
Quoted 3 lines · Jan Engelhardt
Bleh. Except for storage, base 1024 was used for almost everything I remember. 4 MB memory meant 4096 KB, and that's still the case today. Most likely the same for transfer rates.
Nope, transfer rates were initially 1000-based: 9.6 kbps = 9600 bps, 28.8 kbps = 28800 bps, 64 kbps = 64000 bps. Then it went 128, 256, 512 kbps = 512000 bps and 1 Mbps = 2 * 512 kbps = 1024000 bps.
ACK. But this and harddisk sizes are really the only areas.
Quoted 8 lines
But it's limited mostly to serial interfaces. Other networks use 10, 1000 etc. because they have nothing natural in (powers of) 2 so 1 Mbps may be 1000000 bps as well.
Quoted 1 line
It's just that storage vendors broke the computer rule and went with 1000.
1024 etc. is (should be) natural to disks because the sector size is 512 B, 2048 B or something like that.
Yes, but it sounds in commercials better if there is a larger number there. And you can raise the result of a fraction if you lower the divisor.
Bernd
Signature · 3 lines
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and ServicesQuoted 6 lines · Krzysztof Halasa
Quoted 1 line · Jan Engelhardt
It's just that storage vendors broke the computer rule and went with 1000.
1024 etc. is (should be) natural to disks because the sector size is 512 B, 2048 B or something like that.
But other than the sector size there is no natural power of 2 connected to disk size. A disk can have any odd number of sectors.
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 2 lines · Andreas Schwab
But other than the sector size there is no natural power of 2 connected to disk size. A disk can have any odd number of sectors.
But the manufacturers don't count in sectors.
It should be consistent, though. "How many GB of disk space do you need to store 2 GB of USB flash, and how many to store 2 GB RAM image"? :-)
Signature · 1 line
Krzysztof Halasa
Quoted 9 lines · Krzysztof Halasa
Quoted 2 lines · Andreas Schwab
But other than the sector size there is no natural power of 2 connected to disk size. A disk can have any odd number of sectors.
But the manufacturers don't count in sectors.
It should be consistent, though. "How many GB of disk space do you need to store 2 GB of USB flash, and how many to store 2 GB RAM image"?
Here's the marketing gap a company could jump in:
"first to count in real GB"
-`J'
Quoted 6 lines · Krzysztof Halasa
Quoted 2 lines · Andreas Schwab
But other than the sector size there is no natural power of 2 connected to disk size. A disk can have any odd number of sectors.
But the manufacturers don't count in sectors.
The exact number of sectors is often printend on the label.
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 1 line · Andreas Schwab
The exact number of sectors is often printend on the label.
Sure, I'd even say "almost always" for recent disks. Still, they count in GBs, not sectors.
OTOH it would be great if they say "xxx,xxx,xxx 512-byte sectors", and maybe "approx. X GB".
Signature · 1 line
Krzysztof Halasa