this post was submitted on 27 Dec 2023
126 points (68.3% liked)

Technology

59201 readers
3332 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L4s@lemmy.world
L3s@fry.gs
L4s@fry.gs
enu@lemmy.world
126
Why a kilobyte is 1000 and not 1024 bytes (zeta.one)
submitted 10 months ago by wischi@programming.dev to c/technology@lemmy.world
187 comments fedilink hide all child comments
 

I often find myself explaining the same things in real life and online, so I recently started writing technical blog posts.

This one is about why it was a mistake to call 1024 bytes a kilobyte. It's about a 20min read so thank you very much in advance if you find the time to read it.

Feedback is very much welcome. Thank you.

you are viewing a single comment's thread
view the rest of the comments
[–] Bazoogle@lemmy.world 1 points 10 months ago

To me the bigger problem is the fact we don't have a written standard. Idc what people say, but if you buy a 10TB hard drive, then plug it in and the OS doesn't show 10TB, then it can be easy to blame the drive manufacturer when the OS is just using a different prefix quantity, but calling it the same. There should be some way to know exactly how many bytes there are on a drive before you buy it, and it should match when you plug it into your computer. I don't think that's crazy, but the article is a little overboard for that sentiment