Elektrine lite

← Feed

@moof@cupoftea.social

2026-09-22 19:10 UTC

Like, seriously, if you’re going to do that, why not go all the way and redefine the byte as a decabit? How is this saner?

Replies (3)

  • @moof@cupoftea.social 2026-09-22 19:25

    Or in modern gen-z speak: “There are 8.589934592 Gigabits in a Gibibyte” - statements dreamed up by the utterly deranged. They have played us for absolute fools.

    Open ##4808522

  • @moof@cupoftea.social Because the world of IT interacts with the other engineering disciplines, and believe you me, having the SI prefixes alongside the non-IEEE-1541 bit/byte prefixes… Often in the same calculations… (yes, we’ve had cause to calculate kiB/m^2 and scale that to GiB/km^2, and I’ve seen the errors with kB/m^2 to GB/km^2; and then we need to spec and procure storage, on-board (in Spaaaace, so get it right first time ‘cause we’re not getting it back down to fix afters!) or spinning metal/flash on ground). The transition may hurt, but at least the prefixes are still the same factors, just different labels.

    Open ##5105736

  • @andrewg@mastodon.ie 2026-09-23 08:03

    @moof@cupoftea.social let’s do that, and then the number of memory locations addressible by a one decabit pointer is … 2^10 = … 1024 … 🤔

    Open ##5105743