<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Binary confusion: kilobytes and kibibytes</title>
	<atom:link href="http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/</link>
	<description>and I mean it</description>
	<pubDate>Wed, 19 Nov 2008 03:32:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Old Timer</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-270724</link>
		<dc:creator>Old Timer</dc:creator>
		<pubDate>Sat, 19 Jul 2008 04:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-270724</guid>
		<description>I have mixed feelings.  There are points to be considered on both sides of the argument.  One Kilo, Mega, etc are base 10 prefixes in the "metric" system.  Since binary number systems do not have equivalent naming, metric names were "borrowed" to approximate their originally intended values.  50 years ago, a bit (BInary digIT), was the smallest routable/storable unit of data.  Nibbles are 4 bits, bytes (characters) were 8 bits. A double byte (word) was 16 bits.  I suppose double word is 32 bits.  Who knows what 64 or 128 bit chunks are called. BEFORE 1993, it was common knowledge among computer enthusiasts, that KB meant an approximation of KiloBytes equaling 1024 times 8 bits rather than 1000.
Kilo was not a literal metric value, it is/was the closest base two approximation of that value.  The only organizations/manufacturers that did not follow this "standard" were the storage/hard disk companies.  
Most telco, isp, or data networks "used to" measure bandwidth load or throughput in kilobits per second.  Everything computerized acknowledged kilo to mean 1024.  Mega meaning 1048576.  By nature, humans are lazy and like to drop or round off the details.

A Kbyte is an exact value, 1024.  It's name however can be considered inaccurate (get over it, it has been that way since the first computer).  An Mbyte is 1048576.  After 50 years, not 25, you cannot recall text books, documentation, or "common" knowledge.  A Kilo is a 1000 times something true.  Like every rule, there is an exception.  When bit or byte is suffixed to the prefix, the nearest base 2 value applies.  The exception to this rule, is hard disk storage.  They may have won or got the suit dismissed, but that does not make them right.  They just had better lawyers than the class action lawyers.</description>
		<content:encoded><![CDATA[<p>I have mixed feelings.  There are points to be considered on both sides of the argument.  One Kilo, Mega, etc are base 10 prefixes in the &#8220;metric&#8221; system.  Since binary number systems do not have equivalent naming, metric names were &#8220;borrowed&#8221; to approximate their originally intended values.  50 years ago, a bit (BInary digIT), was the smallest routable/storable unit of data.  Nibbles are 4 bits, bytes (characters) were 8 bits. A double byte (word) was 16 bits.  I suppose double word is 32 bits.  Who knows what 64 or 128 bit chunks are called. BEFORE 1993, it was common knowledge among computer enthusiasts, that KB meant an approximation of KiloBytes equaling 1024 times 8 bits rather than 1000.<br />
Kilo was not a literal metric value, it is/was the closest base two approximation of that value.  The only organizations/manufacturers that did not follow this &#8220;standard&#8221; were the storage/hard disk companies.<br />
Most telco, isp, or data networks &#8220;used to&#8221; measure bandwidth load or throughput in kilobits per second.  Everything computerized acknowledged kilo to mean 1024.  Mega meaning 1048576.  By nature, humans are lazy and like to drop or round off the details.</p>
<p>A Kbyte is an exact value, 1024.  It&#8217;s name however can be considered inaccurate (get over it, it has been that way since the first computer).  An Mbyte is 1048576.  After 50 years, not 25, you cannot recall text books, documentation, or &#8220;common&#8221; knowledge.  A Kilo is a 1000 times something true.  Like every rule, there is an exception.  When bit or byte is suffixed to the prefix, the nearest base 2 value applies.  The exception to this rule, is hard disk storage.  They may have won or got the suit dismissed, but that does not make them right.  They just had better lawyers than the class action lawyers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MegaTrooper</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-209765</link>
		<dc:creator>MegaTrooper</dc:creator>
		<pubDate>Fri, 15 Feb 2008 14:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-209765</guid>
		<description>Herb, you can do it yourself! Draw a blue line with a length of 1000 mm. Now draw a parallel red line with a length of 1024 mm. The blue line represents a kilobyte and the red line represents a kibibyte.</description>
		<content:encoded><![CDATA[<p>Herb, you can do it yourself! Draw a blue line with a length of 1000 mm. Now draw a parallel red line with a length of 1024 mm. The blue line represents a kilobyte and the red line represents a kibibyte.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Schaffhausen</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-198542</link>
		<dc:creator>Ben Schaffhausen</dc:creator>
		<pubDate>Fri, 11 Jan 2008 19:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-198542</guid>
		<description>Kilo has meant 1000 since long before "byte" was a term. The people who started using "kilo" to mean 1024 out of convenience were the ones who were wrong- not people trying to set things straight today. 

The problem - "kilo" (and mega, giga, tera, etc) has adopted two usages, one as 1000 (base ten), and one as 1024 (base 2). 

The obvious solution is to adopt a new set of prefixes for the _new_ use, the base-2 usage.  This has been done, let's accept it. 

It's either that or anytime anyone publishes anything using the kilo, mega, giga, tera or larger prefixes in the "small" computer- software/hardware/communications industry they need to put a definition footnote with every usage designating which interpretation they are using.

Until then every time I see the term "MB" I need to ask myself which definition they are using (let alone if they really mean "bytes" or "bits")</description>
		<content:encoded><![CDATA[<p>Kilo has meant 1000 since long before &#8220;byte&#8221; was a term. The people who started using &#8220;kilo&#8221; to mean 1024 out of convenience were the ones who were wrong- not people trying to set things straight today. </p>
<p>The problem - &#8220;kilo&#8221; (and mega, giga, tera, etc) has adopted two usages, one as 1000 (base ten), and one as 1024 (base 2). </p>
<p>The obvious solution is to adopt a new set of prefixes for the _new_ use, the base-2 usage.  This has been done, let&#8217;s accept it. </p>
<p>It&#8217;s either that or anytime anyone publishes anything using the kilo, mega, giga, tera or larger prefixes in the &#8220;small&#8221; computer- software/hardware/communications industry they need to put a definition footnote with every usage designating which interpretation they are using.</p>
<p>Until then every time I see the term &#8220;MB&#8221; I need to ask myself which definition they are using (let alone if they really mean &#8220;bytes&#8221; or &#8220;bits&#8221;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Herb Simmons</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-162882</link>
		<dc:creator>Herb Simmons</dc:creator>
		<pubDate>Wed, 31 Oct 2007 18:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-162882</guid>
		<description>Can someone please, PLEASE! provide, or tell me where to find a simple DRAWING illustrating megabytes to kilobytes? Is that too much to ask? I'll appreciate anything I can get! Anything! I'm at the end of my rope. I ain't real smart. Thanx. Herb</description>
		<content:encoded><![CDATA[<p>Can someone please, PLEASE! provide, or tell me where to find a simple DRAWING illustrating megabytes to kilobytes? Is that too much to ask? I&#8217;ll appreciate anything I can get! Anything! I&#8217;m at the end of my rope. I ain&#8217;t real smart. Thanx. Herb</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-115075</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Mon, 09 Jul 2007 16:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-115075</guid>
		<description>@Lyberty: the proposal does not introduce more ambiguity, its goal is to remedy the existing confusion. In the past, manufacturers used kilo for 1024 and Pluto was a planet. Both historical errors have been corrected. 
@Danix: you defend the 'old' system and by citing the DSL example prove exactly why it is flawed. Confusion about units is what made NASA lose a Mars Orbiter. So just accept it: 'Kilo' is always 1000, Mega is '1000000'.</description>
		<content:encoded><![CDATA[<p>@Lyberty: the proposal does not introduce more ambiguity, its goal is to remedy the existing confusion. In the past, manufacturers used kilo for 1024 and Pluto was a planet. Both historical errors have been corrected.<br />
@Danix: you defend the &#8216;old&#8217; system and by citing the DSL example prove exactly why it is flawed. Confusion about units is what made NASA lose a Mars Orbiter. So just accept it: &#8216;Kilo&#8217; is always 1000, Mega is &#8216;1000000&#8242;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danix</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-115036</link>
		<dc:creator>Danix</dc:creator>
		<pubDate>Mon, 09 Jul 2007 15:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-115036</guid>
		<description>Actually, capital-K for the positive power is only used in IT, as in the SI definition "K" is for Kelvin. The other positive powers do use uppercase :)

As for kilo/kibi, I agree with the above poster that the proposal is actually backwards! For bytes, the measure has been and always will be 2^10, 2^20, etc. because of one simple thing: computers use binary, not decimal. Also, the term sounds corny, I actually thought someone had made a joke on the article where the definition was.

The only renegade dudes on this issue were the HD manufacturers, but that was because they were taking advantage of the "ambiguity". The only place where kilo=1000 in the SI sense is when talking about data transfer (kilobits, megabits) and even then it isn't always used: my ISP gives me 1Mbps, and my DSL router shows 1024Kbps as my download link speed.

Me thinking about "Kirby-bytes" when I see that mock prefix...</description>
		<content:encoded><![CDATA[<p>Actually, capital-K for the positive power is only used in IT, as in the SI definition &#8220;K&#8221; is for Kelvin. The other positive powers do use uppercase <img src='http://blog.forret.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>As for kilo/kibi, I agree with the above poster that the proposal is actually backwards! For bytes, the measure has been and always will be 2^10, 2^20, etc. because of one simple thing: computers use binary, not decimal. Also, the term sounds corny, I actually thought someone had made a joke on the article where the definition was.</p>
<p>The only renegade dudes on this issue were the HD manufacturers, but that was because they were taking advantage of the &#8220;ambiguity&#8221;. The only place where kilo=1000 in the SI sense is when talking about data transfer (kilobits, megabits) and even then it isn&#8217;t always used: my ISP gives me 1Mbps, and my DSL router shows 1024Kbps as my download link speed.</p>
<p>Me thinking about &#8220;Kirby-bytes&#8221; when I see that mock prefix&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rav0</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-129</link>
		<dc:creator>rav0</dc:creator>
		<pubDate>Wed, 04 Jan 2006 23:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-129</guid>
		<description>To above:
Conventionally, the capital letter is always used in the positive powers, and lowercase in negative powers.</description>
		<content:encoded><![CDATA[<p>To above:<br />
Conventionally, the capital letter is always used in the positive powers, and lowercase in negative powers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-128</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 14 Nov 2005 17:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-128</guid>
		<description>I think you should use k for the kilo prefix instead of K.</description>
		<content:encoded><![CDATA[<p>I think you should use k for the kilo prefix instead of K.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lyberty</title>
		<link>http://blog.forret.com/2005/02/binary-confusion-kilobytes-and-kibibytes/#comment-127</link>
		<dc:creator>lyberty</dc:creator>
		<pubDate>Sat, 22 Oct 2005 10:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2005/02/04/binary-confusion-kilobytes-and-kibibytes/#comment-127</guid>
		<description>You wrote "Well, clarity is a good reason, and unambiguity."

The problem is that the IEC's proposal INTRODUCES MORE AMBIGUITY because it attempts to change EXISITING definitions. In other words, the documentation of the last 25 or so years becomes unclear as the reader now has to ask himself/herself "Is this use of 'MB' in this text the IEC definition, or the original definition? One can only assume that they redefined KB, MB, and GB because they wanted the prefixes to be consistent with the other (standardized) uses, but the better solution would have been, instead, to create new terms for the less common usage of base-10 for KB/MB/GB/etc. (i.e. "kibi-" meaning 1,000 instead of "kibi-" meaning 1,024). See lyberty.com/encyc/articles/kb_kilobytes.html</description>
		<content:encoded><![CDATA[<p>You wrote &#8220;Well, clarity is a good reason, and unambiguity.&#8221;</p>
<p>The problem is that the IEC&#8217;s proposal INTRODUCES MORE AMBIGUITY because it attempts to change EXISITING definitions. In other words, the documentation of the last 25 or so years becomes unclear as the reader now has to ask himself/herself &#8220;Is this use of &#8216;MB&#8217; in this text the IEC definition, or the original definition? One can only assume that they redefined KB, MB, and GB because they wanted the prefixes to be consistent with the other (standardized) uses, but the better solution would have been, instead, to create new terms for the less common usage of base-10 for KB/MB/GB/etc. (i.e. &#8220;kibi-&#8221; meaning 1,000 instead of &#8220;kibi-&#8221; meaning 1,024). See lyberty.com/encyc/articles/kb_kilobytes.html</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.378 seconds -->
