zlacker

[return to "1 kilobyte is precisely 1000 bytes?"]
1. waffle+pC[view] [source] 2026-02-03 19:24:06
>>surpri+(OP)
The author decidedly has expert syndrome -- they deny both the history and rational behind memory units nomenclature. Memory measurements evolved utilizing binary organizational patterns used in computing architectures. While a proud French pedant might agree with the decimal normalization of memory units discussed, it aligns more closely to the metric system, and it may have benefits for laypeople, it fails to account for how memory is partitioned in historic and modern computing.
◧◩
2. ozozoz+mY[view] [source] 2026-02-03 21:05:19
>>waffle+pC
It’s not them denying it, it’s the LLM that generated this slop.

All they had to say was that the KiB et. al. were introduced in 1998, and the adoption has been slow.

And not “but a kilobyte can be 1000,” as if it’s an effort issue.

◧◩◪
3. kevin_+Uv1[view] [source] 2026-02-04 00:06:15
>>ozozoz+mY
They are managed by different standards organizations. One doesn't like the other encroaching on its turf. "kilo" has only one official meaning as a base-10 scalar.
◧◩◪◨
4. dietr1+oP1[view] [source] 2026-02-04 02:15:15
>>kevin_+Uv1
I don't think of base 10 being meaningful in binary computers. Indexing 1k needs 10 bits regardless if you wanted 1000 or 1024, and the base 10 leaves some awkward holes.

In my mind base 10 only became relevant when disk drive manufacturers came up with disks with "weird" disk sizes (maybe they needed to reserve some space for internals, or it's just that the disk platters didn't like powers of two) and realised that a base 10 system gave them better looking marketing numbers. Who wants a 2.9TB drive when you can get a 3TB* drive for the same price?

[go to top]