There is a counterproductive obsession with powers of 10. Sometimes, other systems just make more sense. For example, for time, or angles, or bytes. There are properties of certain numbers (or bases) that make everything descending from them easier to deal with. for angles and time (and feet): https://en.wikipedia.org/wiki/Superior_highly_composite_numb... For other problems we use base 2, 3, 8, 16, or 10. Must we tr…
Now that I think about it, I see KiB and kb all the time but I don't know that I've ever encountered Kib or kB in the wild. Maybe I'm in a bubble? Or maybe we should accept that kb is power of 10 but kB is power of two? Well I guess we already basically have this in practice since Ki can be shortened to K seeing as metric prefixes are always lower case and we clearly aren't talking about kelvin bytes.
1 kilobyte is precisely 1000 bytes?
321–330 of 430 posts
Re: 1 kilobyte is precisely 1000 bytes?
#322Re: 1 kilobyte is precisely 1000 bytes?
#323Earlier quoted context omitted.
Knuth is not in favour of using kilo/mega/etc with power-of-2 meanings: > I'm a big fan of binary numbers, but I have to admit that this convention flouts the widely accepted international standards for scientific prefixes. He also calls it “an important issue” and had written “1000 MB = 1 gigabyte (GB), 1000 GB = 1 terabyte (TB), 1000 TB = 1 petabyte (PB), 1000 PB = 1 exabyte (EB), 1000 EB = 1 zettabyte (ZB), 1000 Z…
It's odd though. Metric prefixes are always lower case, so GB isn't valid metric. Further, outside of storage manufacturers attempting to inflate their numbers when does is ever make sense to mix power of ten with 8 bit bytes? Networking is always in bits per second, not bytes. Edit: Disregard the metric bit but I think the rest still stands.
Re: 1 kilobyte is precisely 1000 bytes?
#324Again? 1 kB is 1024 B. It's measurement unit thing. Not logics. 8 bits in a byte. Not 10, neither 6 nor 5. Just 8. Like feet in yards, inches in feet, meters in kilometers and ounces in pounds. It's 1024. Period. Then of course you are free to count as many bytes as you want and call that bunch a kB. Pretending anyone else will agree on that is a different thing.
Re: 1 kilobyte is precisely 1000 bytes?
#325Earlier quoted context omitted.
All words are made up. They weren’t handed down from a deity, they were made up by humans to communicate ideas to other humans. “Kilo” can mean what we want in different contexts and it’s really no more or less correct as long as both parties understand and are consistent in their usage to each other.
> “Kilo” can mean what we want in different contexts Fair enough. 1000 watts is a kilowatt 1000 hertz is a kilohertz 1000 metres is a kilometre 1000 litres is a kilolitre 1000 joules is a kilojoule 1000 volts is a kilovolt 1000 newtons is a kilonewton 1000 pascals is a kilopascal 1024 bytes is a kilobyte, because that's what we're used to and we don't want to change to a new prefix
Re: 1 kilobyte is precisely 1000 bytes?
#326Re: 1 kilobyte is precisely 1000 bytes?
#327Earlier quoted context omitted.
Yes, tomato's ARE actually a fruit. But really!? I'll keep calling it in nice round powers of two, thank you very much.
Yes. Tomatoes are a fruit because the science says so. That non-scientific people call it something else does not change facts.
I would argue fruit and fruit are two words, one created semasiologically and the other created onomasiologically. Had we chosen a different pronunciation for one of those words, there would be no confusion about what fruits are.
[0] - https://en.wikipedia.org/wiki/Fruit#Botanical_vs._culinary
Re: 1 kilobyte is precisely 1000 bytes?
#328Earlier quoted context omitted.
...old lazy and wrong! Capital K is for Kelvin.
>Capital K is for Kelvin. It should be "kelvin" here. ;) Unit names are always lower-case[1] (watt, joule, newton, pascal, hertz), except at the start of a sentence. When referring to the scientists the names are capitalized of course, and the unit symbols are also capitalized (W, J, N, Pa, Hz). [1] SI Brochure, Section 5.3 "Unit Names" https://www.bipm.org/documents/20126/41483022/SI-Brochure-9-...
Re: 1 kilobyte is precisely 1000 bytes?
#329The meaning of kilo, mega, giga, tera, etc. are unambiguous: SI prefixes defined as powers of 10, not 2. 1 TB is 10*12 bytes, not 2*40 bytes. The misuse of those prefixes as powers of 1024, while useful as shorthand for computer memory where binary addressing means, is still exactly that: a misuse of SI prefixes. There's now a separate set of base-2 prefixes to solve this, and people need to update their language acc…
Just because an official body gives a single definition doesn't mean it's unambiguous. Real communication isn't bound by official bodies. When I say my computer has 16GB of RAM, that does not mean exactly 16 billion bytes. I need to update my language accordingly? No thanks. I'll keep saying what I say and nothing will happen.
Re: 1 kilobyte is precisely 1000 bytes?
#330Looking around their website, they appear to be an enthusiastic novice. I looked around because isn't a hardware architecture course part of any first year syllabus? The author clearly hasn't a clue about hardware, how memory is implemented.
I'm the author. Actually I'm quite familiar how memory addressing works, including concepts related to virtual memory / memory paging. Yes, I'm not a "low-level nerd" with deep knowledge in OS, hardware or machine code / assembly, but I know enough basics. And yes, I already mentioned that binary addressing makes more sense in RAM (and most of the hardware), and yes, I would not expect 4000-byte memory pages or disk clusters.
My main points are:
1) Kilo, mega, etc. prefixes are supposed to be base 10 instead of base 2, but in tech industry they are often base 2.
2) But this isn't the worst part. While we could agree on 1024 magnitude for memory, the problem is that it's still used inconsistently. Sometimes kilobyte is 1024 bytes, sometimes it's 1000. And this causes a confusion. In some contexts, such as RAM stick or disk cluster, you can assume base 2, but in some other contexts, such as file size, it's ambiguous. For example, would it be good if Celsius meant different things? I don't think so, it would certainly complicate things.