zlacker

[parent] [thread] 6 comments
1. bigstr+(OP)[view] [source] 2026-02-03 18:13:00
In computers, "kilobyte" has a context dependent meaning. It has been thus for decades. It does not only mean 1000 bytes.
replies(1): >>pif+X1
2. pif+X1[view] [source] 2026-02-03 18:21:00
>>bigstr+(OP)
I understand the usual meaning, but I use the correct meaning when precision is required.
replies(2): >>wvenab+me >>zephen+Og
◧◩
3. wvenab+me[view] [source] [discussion] 2026-02-03 19:07:13
>>pif+X1
That's funny. If I used the "correct" meaning when precision was required then I'd be wrong every time I need to use it. In computers, bytes are almost always measured in base-2 increments.
◧◩
4. zephen+Og[view] [source] [discussion] 2026-02-03 19:17:21
>>pif+X1
When dealing with microcontrollers and datasheets and talking to other designers, yes precision is required, and, e.g. 8KB means, unequivocally and unambiguously, 8192 bytes.
replies(1): >>kstrau+Fz
◧◩◪
5. kstrau+Fz[view] [source] [discussion] 2026-02-03 20:42:11
>>zephen+Og
Ummm, should we tell him?
replies(1): >>zephen+aC
◧◩◪◨
6. zephen+aC[view] [source] [discussion] 2026-02-03 20:53:08
>>kstrau+Fz
That I can't type worth shit?

Yeah, I already knew that, lol.

But thanks for bringing it to my attention. :-)

replies(1): >>kstrau+BC
◧◩◪◨⬒
7. kstrau+BC[view] [source] [discussion] 2026-02-03 20:55:14
>>zephen+aC
I kid good-naturedly. I'm always horrified at what autocorrect has done to my words after it's too late to edit or un-send them. I swear I write words goodly, for realtime!
[go to top]