That doesn't make any sense. You need to be using imperial volumes.
1 tablespoonbyte is approximately 36 bits (I just counted, with couscous, the universal measure), which makes a pintbyte is 1152 bytes- about a kilobyte, but also the number of pixels across on my screen.
It also gives us a gallonbyte - just shy of 10 kilobytes at 9216 bytes. That's even more convenient, because it's square root is 96.
Of course, having a hogsheadbyte at 442368- well, I think even you will find it difficult to argue the usefulness of finally being able to use a multiple of 442368.
Finally, we've got the tunbyte: 2322432. Nobody will ever need more than about 28% of a tunbyte of memory, so you see it scales out at just the most convenient point for us here.
Comments
That doesn't make any sense. You need to be using imperial volumes.
1 tablespoonbyte is approximately 36 bits (I just counted, with couscous, the universal measure), which makes a pintbyte is 1152 bytes- about a kilobyte, but also the number of pixels across on my screen.
It also gives us a gallonbyte - just shy of 10 kilobytes at 9216 bytes. That's even more convenient, because it's square root is 96.
Of course, having a hogsheadbyte at 442368- well, I think even you will find it difficult to argue the usefulness of finally being able to use a multiple of 442368.
Finally, we've got the tunbyte: 2322432. Nobody will ever need more than about 28% of a tunbyte of memory, so you see it scales out at just the most convenient point for us here.