KiB was defined decades ago… Way back in 1999. Before that it was not well defined. kb could mean binary or decimal depending on what or who was doing the measurements.
And? I started programming back in 1996, back when most computer storage and memory measurements were generally already well defined, around the base 2 binary system.
Floppy disks were about the only exception, 1.44MB was indeed base 10, but built on top of base 2 for cluster size. It was indeed a clusterfuck. 1.44MB was technically 1.38MiB when using modern terms.
I do wonder sometimes how many buffer overflow errors and such are the result of ‘programmers’ declaring their arrays in base 10 (1000) rather than base 2^10 (1024)… 🤔
I’m not all about jamming a random i into terminology that was already well defined decades ago. But hey, you go for it if that’s what you prefer.
By the way, ‘for FTW’ makes about as much sense as saying ‘ATM machine’, it’s redundant.
yup! serves me right for responding while rushing out of the door. gonna leave that here for posterity.
edit: and… switching networks managed to triple post this response. i think thats enough internet for today.
LOL, redundancy FTW 👍😂🤣
Smh my head
KiB was defined decades ago… Way back in 1999. Before that it was not well defined. kb could mean binary or decimal depending on what or who was doing the measurements.
And? I started programming back in 1996, back when most computer storage and memory measurements were generally already well defined, around the base 2 binary system.
Floppy disks were about the only exception, 1.44MB was indeed base 10, but built on top of base 2 for cluster size. It was indeed a clusterfuck. 1.44MB was technically 1.38MiB when using modern terms.
I do wonder sometimes how many buffer overflow errors and such are the result of ‘programmers’ declaring their arrays in base 10 (1000) rather than base 2^10 (1024)… 🤔
deleted by creator
deleted by creator
yup! serves me right for responding while rushing out of the door. gonna leave this here for posterity.