• Victor@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    19 hours ago

    I don’t know why he has such trouble. You really should only need 1 bit to determine whether or not it’s afternoon. Just look at the “afternoon” bit light. 🤷‍♂️

      • Victor@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        15 hours ago

        You only need four bits to represent 12 (actually 16), add 1 extra bit to double that for the am/pm bit. Any bit can represent anything you like if you encode it as such. 👍

        • bdonvr@thelemmy.club
          link
          fedilink
          arrow-up
          3
          ·
          15 hours ago

          Sure but if you’re on Binary time surely you’ve ditched the stupid AM/PM thing and use 24 hour time

          • Victor@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            14 hours ago

            It does sound counterintuitive, doesn’t it. It’s actually the opposite of what you’d expect, at least in my case.

            When I wrote my own binary clock I first tried using one 5-bit word to visually represent 0–23, and another 6-bit word to represent 0–59. But I found it hard to quickly read at a glance. Especially the minutes.

            I found the 4-bit representation of 1–12 simpler to read at a glance, and then use the 5th bit to represent am/pm. In fact, I could skip the am/pm bit completely, because who tf doesn’t know whether it’s before or after noon when looking at a 12h clock, unless you’re in complete isolation from the outside.

            Then, obviously 6 bits for the minutes is even harder to glance, and more noise, so I made that into a 2-bit thing where the most significant bit is whether or not we are past the half hour, and the least significant bit represents whether or not we are past the 15 or 45-minute mark, which tells me which quarter of the hour we are in. It served me enough granularity to be on time for meetings etc. 😄