• Powderhorn@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    3
    ·
    edit-2
    2 months ago

    Dear god, are we still using base 2 for file sizes? At least use TiB like a reasonable person.

      • Powderhorn@beehaw.org
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        2 months ago

        To be clear, I’m fine with RAM being base 2 – it’s rather difficult for it not to be given the structure – but for fixed storage, this is an old-school measurement that only gets worse with each order of magnitude.

        • thingsiplay@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          I don’t have a problem with bits or bytes as the unit. Both are valid and widely used. There was no problem with the reply using TB instead TiB, until you made it. I get it in case when it really matters, but don’t see here to force using TiB instead. Both are valid and correct and there is no problem in this case.

    • interdimensionalmeme@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      I don’t remember which is the stupid “1024 bytes in a kilobyte” one but
      745,450,666,761,889 byte is 745 terabytes, that should be 745 TB and that 678 should be what TiB is for
      And also that entire 677.98 is a useless value, there’s nothing that is “677” about this

      • Powderhorn@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        It is if you just truncate! No one should do this, as I don’t recall the last time I saw such a textbook example of “rounding error” meaning “we fucked up while rounding.”