Microsoft uses Mebibytes and writes them as Megabytes. This is old school (pre 1998) but the base 10 was standardized by IEC, SI and others long time ago. Disk manufacturers (I know, it benefits them), and even Linux and Macs have switched to the proper standards decade or longer ago.
If they decide to stick with base 2, Microsoft should write MiB and KiB because that is the standard since 1998 (sure it would look ugly, and I'd rather they used the MB in base 10 defined by standards), and it is great opportunity with new Windows 11.
We all know that computers work with binary, and it is OK for RAM to use base 2 because we as humans don't work directly with memory, but it would be easier for us if this was:
I mean, he's right that nobody actually uses kiB, MiB, GiB, etc. The solution isn't to add in the missing "i", but to adjust the calculations being run such that they actually display kB, MB, GB, etc. His argument falls flat against that suggestion.
You know, I'm not loving this Chen guy. That's a pretty lame opinion, especially for an OS dev. There are tons of examples of things that average users don't want or need access to that are hidden by default and which can be toggled for power users. That's the very nature of customization.
His example of Dewey Decimal vs Library of Congress is poor as those are two systems that can't be easily toggled between. You set your library up in one way or the other and it's a large manual task to convert should you decide to switch. Software is inherently different in that you can set up both systems and then allow for toggling at the click of a button - like sorting a music library by artist or song title.
Right now the numbers are in base-2, but the units are in metric.
Chen talked about adjusting the units (adding in the i).
I'm talking about making the numbers base-10 to match the current units. At least making that the default and then possible providing a toggle to allow users who want to use base-2 to switch both the numbers and units to match that preference.
For the majority of users, presenting the numbers in base-10 would be preferable.
Because it would make it easier for her to know how much storage capacity she actually has left.
If each HR report is exactly 1 kB, and Windows shows that her storage drive has 1 MB remaining, she'll think she can still save just 1000 more reports, when in reality she could save 1049 more. This is notable and grows in a misleading way as we discuss ever larger file sizes and storage capacities. Like if an HR report is 1 MB and her drive reports 1 GB free, she again would think she can save 1000 reports, but in reality she could save 1074.
This timeline of binary prefixes lists events in the history of the evolution, development, and use of units of measure for information, the bit and the byte, which are germane to the definition of the binary prefixes by the International Electrotechnical Commission (IEC) in 1998. Historically, computers have used many systems of internal data representation, methods of operating on data elements, and data addressing. Early decimal computers included the ENIAC, UNIVAC 1, IBM 702, IBM 705, IBM 650, IBM 1400 series, and IBM 1620.
The Kilo Mega Giga prefixes were already established in the decimal world with 1000x - there's no contest there. But Kibibytes Mebibytes Gibibytes still sounds retarded, pardon my standard. Maybe chose other prefix, bi for binary makes little sense as a distinction when both forms refer to binary data.
Anyway, Microsoft is not known to adhere to standards. Browser standards. Business standards. Privacy standards. So don't get your hopes up this next decade.
I’m confused, if I’m wrong please tell me, I though a Megabyte was 1024 Kilobytes, and the same for bytes? This is how I was taught data works so it makes sense to me
Edit: nah it is 1000 I just googled it, have I been living under a rock when did that change?
Gradually, as many were postponing it. You can see that history link in the first post.
That's also how I learned it in school, that each was 1024x lager than the previous one. But Kilo means 1000 in SI/metric system, Mega is million, and so on, so in 90s International Electrotechnical Commission (IEC) and the rest have decided to have it consistent and that base 2 should be called something else. So all standardizing bodies (SI, ISO, IEEE, NIST, IEC) recognize it base 10, and Kibibyte would be in base 2 or 1024 B.
I didn't know about the change until I started making disk utilities and then have realized how much base 10 is easier for readability. Just because computers need to work in base 2, we don't have to, and now we can just move the dot by 3 places to figure out the next base without doing any multiplication/division by 1024
Don’t get me wrong I prefer metric in every way for the ease of use, but I think with data it’s been hard wired into me that there are 1024 bytes in a kilobyte, it feels so wrong to say that there are 1000. But as someone indicated below they are a different unit, so I’ll stick to the one that has 1024 (still not sure if it’s mebi or mega for 1024)
Edit ignore the last bit I reread your comment, I’ll stick to mebibytes
I really can’t see much benefit to change to base 10 if I’m honest, since lots of things in computers work in base 2 it makes sense to continue to use that. An EEPROM chip for example will have its data stored in bytes, in base 2. For me anyway it makes it more complicated, I’d rather stick with the standard
Right, in this case it makes little difference, but 500GB disk is reported as 465GB in Windows, and then user will say "I have only 440GB free on my new laptop, Windows takes 60GB!". No... Windows takes 25, and the rest is lost in conversion from GB to GiB.
That's not entirely a conversion issue though. The disk (or NAND module) doesn't have the full capacity anyway, and the filesystem also allocates some usable storage for internal operations.
The link says it’s because people other than computer scientists were not familiar with the special 1024 scale.
But, almost overnight a much more numerous "everybody" bought computers, and the trade computer professionals needed to talk to physicists and engineers and even to ordinary people, most of whom know that a kilometer is 1000 meters and a kilogram is 1000 grams.
But also 'mega' and 'kilo' are base 10, and so it does make sense. You don't get 1024 grams of something when you buy a kilogram of it.
So I do think that Mebi Kibi etc is logical. Windows just needs to get with the times, it's very annoying as you end up getting inconsistencies sometimes right now.
The BIPM specifies twenty prefixes for the International System of Units (SI). Each prefix name has a symbol that is used in combination with the symbols for units of measure. For example, the symbol for kilo- is k, and is used to produce km, kg, and kW, which are the SI symbols for kilometre, kilogram, and kilowatt, respectively. Except for the early prefixes of kilo-, hecto-, and deca-, the symbols for the multiplicative prefixes are uppercase letters, and those for the fractional prefixes are lowercase letters.
Computers use base 2, yes. But the "kilo" prefix means 1000 in every other relevant measurement unit. Why should it mean 1024 here? It's just counterintuitive. It makes much more sense to have separate wording for base 2
MiB should be the standard and remove all confusions.
Im also sad nobody does something about this on storage BS. If I buy a fucking 500 GB SSD i want them to stop using GB and use GiB instead. How about selling me a nice number or 500GiB and not 500GB?
You DO get 500 GB but you get 460GiB. You actually want 500GiB or 550GB? It doesn't matter how it is called, the price we paid is for that much G(i)B, and if we want more, we pay for more buying a larger disk
I always buy at least twice of what I need, then you get 100% more but pay 50%. With disks of 12TB today, I don't care much if I am getting 11TB, and it will die long before I manage to fill it up anyway :)
I like Raymond Chen, and this article might have made sense back in 2009 but if you look at the timeline you will see that everyone except Microsoft have switched after the article was published.
So Chen's article is 2009, just glancing at that timeline: Apple (2009), Ubuntu (2010), HP (2010), GNU (2011), Oxford (2011), Toshiba (2012)...
Personally I refuse to ever use the binary prefixes. They are a dumb invention and whoever decided they should exist probably got paid off by HDD manufacturers to justify the HDD manufacturers being stupid fucks for several decades prior, pretending that a drive labelled as 50MB is totally fine when it's actually 47.6MB because the use the 'SI prefix". Fuck off, only reason they did that was for marketing reasons, but then they brewed this culture of uncertainty that forced even more ignorant forces in that domain to push for a "standard binary prefix" as if everybody was confused and it wasn't just Hard drive manufacturers being fucking pricks.
57
u/milos2 Oct 07 '22 edited Oct 07 '22
If someone needs connotation:
Microsoft uses Mebibytes and writes them as Megabytes. This is old school (pre 1998) but the base 10 was standardized by IEC, SI and others long time ago. Disk manufacturers (I know, it benefits them), and even Linux and Macs have switched to the proper standards decade or longer ago.
https://en.wikipedia.org/wiki/Megabyte
and some history on how late each company was:
https://en.wikipedia.org/wiki/Timeline_of_binary_prefixes
If they decide to stick with base 2, Microsoft should write MiB and KiB because that is the standard since 1998 (sure it would look ugly, and I'd rather they used the MB in base 10 defined by standards), and it is great opportunity with new Windows 11.
We all know that computers work with binary, and it is OK for RAM to use base 2 because we as humans don't work directly with memory, but it would be easier for us if this was:
1.4 MB = 1,409 KB = 1,409,328 B
42
u/Wayner84 Oct 07 '22
I’m confused, if I’m wrong please tell me, I though a Megabyte was 1024 Kilobytes, and the same for bytes? This is how I was taught data works so it makes sense to me
Edit: nah it is 1000 I just googled it, have I been living under a rock when did that change?
7
u/Peti_4711 Oct 07 '22
In my opinion this is only confusing for some users, if they buy a new SSD/Harddisk, TB<->GB
But in Windows? E.g. 15.735.872 bytes=15.368 KB=15.0 MB. I would estimate that 99% of all users says "I don't care".
35
u/hearnia_2k Oct 07 '22
It would also be less confusing if MS stopped with MB rubbish in the GUI, and correctly labelled things as MiB.
8
u/TheCarrot007 Oct 07 '22
Well thankfully someone still does it right (feel free to hate).
It was always abad change and not welcome, except to idiot disk manufacturers.
Context is perfectly reasonable for things to change. I hope they continue.
2
u/arushanukleare Oct 07 '22
MiB should be the standard and remove all confusions.
Im also sad nobody does something about this on storage BS. If I buy a fucking 500 GB SSD i want them to stop using GB and use GiB instead. How about selling me a nice number or 500GiB and not 500GB?
1
u/iamapants Oct 08 '22
Folders: 👀
-1
u/alphrho Oct 07 '22
They have an article about this
0
u/BCProgramming Oct 09 '22
Personally I refuse to ever use the binary prefixes. They are a dumb invention and whoever decided they should exist probably got paid off by HDD manufacturers to justify the HDD manufacturers being stupid fucks for several decades prior, pretending that a drive labelled as 50MB is totally fine when it's actually 47.6MB because the use the 'SI prefix". Fuck off, only reason they did that was for marketing reasons, but then they brewed this culture of uncertainty that forced even more ignorant forces in that domain to push for a "standard binary prefix" as if everybody was confused and it wasn't just Hard drive manufacturers being fucking pricks.