• d00phy
    link
    fedilink
    English
    43 hours ago

    First question, and it’s important: Are you Doc Brown?

  • @SCmSTR@lemmy.blahaj.zone
    link
    fedilink
    English
    4
    edit-2
    3 hours ago

    Neither.

    It’s pronounced: “one and thirty-two hundreths of a megabyte”. Properly.

    But idgaf how you pronounce it as long as I understand exactly what you’re saying. Personally, “one point three two”.

  • Christian
    link
    fedilink
    English
    145 hours ago

    The first one is correct as others have said, but the second one is not ambiguous enough to confuse anyone nor weird enough for anyone to bat an eye at, you’re fine with either.

    • Neko the gamer
      link
      fedilink
      -3
      edit-2
      4 hours ago

      I’d say the second one is more correct, it sounds so weird pronouncing the digits singularly

      • comfy
        link
        fedilink
        5
        edit-2
        3 hours ago

        I’d say the second one is more correct

        In this case, it’s not about what sounds good or personal opinion, there is a standard name for that number for a reason. If I go around calling 100 “one oh oh” or “tenty ten”, it’s clear what number I mean but I can’t honestly call it more correct, because there’s a standard English name for it.

        To demonstrate a part of why it’s clearer that way, put these numbers in ascending numerical order: (e.g. 1, 2, 3, … )

        • one point three
        • one point twenty-nine
        • one point thirty
        • one point thirty-one
        • one point three-thousand-and-fifty-two

        Hopefully this clarifies that we’re not actually dealing with a “thirty-two” when we’re talking about 1.32 (edit: that said, when we’re talking about version numbers, e.g. Linux kernel 4.20, which is greater than Linux kernel 4.9, then we’d say “four point twenty”)

  • @communism@lemmy.ml
    link
    fedilink
    95 hours ago

    One point three two, or one three two if it’s obvious from context where the decimal point is. That’s how you’re meant to pronounce digits after the decimal point in general.

  • @deur@feddit.nl
    link
    fedilink
    98 hours ago

    I agree that the precision is not that valuable as some have said. I’d just read the numbers off as one point two three megabytes since anyone who cares can reconstruct the number, anyone who doesn’t can stick to the first few sig figs.

    For 257.62 GB I’d say “two hundred fifty seven point six two”. Yep. I put in the effort for the most significant of the digits, I dont bother beyond that.

    8249.19 GB? About 8 terabytes. Doesnt really matter anymore.

  • @EvilBit@lemmy.world
    link
    fedilink
    2910 hours ago

    I grew up with science classes telling us always state the digits individually. One point three two.

    • Scrubbles
      link
      fedilink
      English
      69 hours ago

      Math class taught me to be precise I should always say “1 and 32 hundredths Megabytes”

      • comfy
        link
        fedilink
        53 hours ago

        I don’t think that’s any more precise, just more verbose (read: inefficient).

    • @blackbrook@mander.xyz
      link
      fedilink
      79 hours ago

      The only way you could use ‘thirty two’ correctly for that number would be ‘one and thirty two hundredths’ which would be pretty unusual.

    • @SatyrSack@feddit.org
      link
      fedilink
      English
      5
      edit-2
      9 hours ago

      Agree. For things like semantic versioning, in which “1.20.1” and “1.2.1” are two different things, you want to pronounce them “one point twenty point one” and “one point two point one”, respectively. But that is a bit of an outlier. File size should be pronounced “normally”, because “1.20” and “1.2” are the same value.

        • comfy
          link
          fedilink
          23 hours ago

          I disagree. I would personally find one point two zero point one to be more natural and easier to understand.

          I disagree with that, because we’re dealing with a number and not a fraction. Linux kernel 4.20 is not equal to Linux kernel 4.2, we’re actually dealing with the integer 20 here. (yes, alphabetical sorting on a download server has lead me to download an outdated kernel version once)

          • @WeirdGoesPro@lemmy.dbzer0.com
            link
            fedilink
            148 minutes ago

            Don’t you know that my head canon is universal canon? /s

            You make a compelling point. I concede to your logic, but refuse to change my ways.

        • @davidgro@lemmy.world
          link
          fedilink
          46 hours ago

          In that case it’s actually the twentieth (or more likely twenty first) minor version though, it’s not actually a decimal

  • @Valmond@lemmy.world
    link
    fedilink
    119 hours ago

    I mostly heard it one point thirty two? Grew up in Sweden, living in France. If someone says one point three two I’d assume they’re Americans.

    I might be totally wrong, just stating what I have heard

    • @pipes@sh.itjust.works
      link
      fedilink
      36 hours ago

      I had the same experience (also European), but didn’t know the Americans changed it specifically for bytes

      • @lolcatnip@reddthat.com
        link
        fedilink
        English
        23 hours ago

        We don’t. That’s just the normal way most people pronounce numbers with a decimal point. The big exception is prices: $1.32 is often pronounced “one thirty two”.

    • @tetris11@lemmy.mlOP
      link
      fedilink
      49 hours ago

      No that’s interesting, I was wondering if there was a cultural divide.

      Thirty two sounds so alien to me, but I heard it in a Nerdstalgic video and wondered if it was an American thing

    • TheRealKuni
      link
      fedilink
      English
      64 hours ago

      “about a meg” because it’s almost unthinkable anyone cares about 3 tenths of a meg much less 2 hundredths.

      Tell me you never used floppy discs as a storage medium without telling me.

    • @notarobot@lemm.ee
      link
      fedilink
      1
      edit-2
      8 hours ago

      I’d round up to one and a half. Also remove “bytes” and “bites”. 1.32 MB is “one and a half megs” or even “a meg and a half”