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.

        • wischi@programming.devOP
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          9
          ·
          edit-2
          10 months ago

          So why don’t they just label drives in Terabit instead of terabyte. The number would be even bigger. Why don’t Europeans also use Fahrenheit, with the bigger numbers the temperature for sure would instantly feel warmer 🤣

          Jokes aside. Even if HDD manufacturers benefit from “the bigger numbers” using the 1000 conversation is the objectively only correct answer here, because there is nothing intrinsically base 2 about hard drives. You should give the blog post a read 😉

          • wewbull@feddit.uk
            link
            fedilink
            English
            arrow-up
            4
            ·
            10 months ago

            there is nothing intrinsically base 2 about hard drives

            Yes there is. The addressing protocol. Sectors are 512 (2⁹) bytes, and there’s an integer number of them on a drive.

            • wischi@programming.devOP
              link
              fedilink
              English
              arrow-up
              0
              arrow-down
              8
              ·
              10 months ago

              That’s true but the entire disk size is not an exact power of two that’s why binary prefixes (1024 conversation) don’t have any benefit whatsoever when it comes to hard drives. With memory it’s a bit different because other than with storage devices RAM size is always exactly a power of two.