I see what you're saying, but I say you're wrong. 100 megabit/sec is the same thing as 12.5 megabyte/sec (assuming a byte is 8 bits). The problem is people who don't understand that not all of that bandwidth is dedicated to moving the data itself. And if they're really so inclined, just pretend a byte is 10 bits, usually gets a fairly accurate estimate transfer speeds for me.

I also made a Python script for file sizes. At first you could specify 3 choices for KB size: 1024, 1000 and 1012. Later I changed it to leave it up to the user to specify KB size (unfortunately 1024J is not possible to compute with my script. The intel kilobyte is, though. 1,000,000 bytes is 976.622 kb.)

They all sound ridiculous; you're just used to some of them. Even if you coders refuse to say "kibibyte" or "kilobinary byte", and you read both "kB" and "KiB" as "kilobyte", when you're developing software, please use the correct unit symbols, for the benefit of all of us.

I happen to have implemented the XKCD standard for file size units in KDE (http://pastebin.ca/1482983). Thought I'd share the patch here, for those of you who are tired of the IEC standard KDE currently uses. And it's only a -7.7i KiB patch. (For best results, apply to KDE 4.3 or 4.4.)

416365416c wrote:I happen to have implemented the XKCD standard for file size units in KDE (http://pastebin.ca/1482983). Thought I'd share the patch here, for those of you who are tired of the IEC standard KDE currently uses. And it's only a -7.7i KiB patch. (For best results, apply to KDE 4.3 or 4.4.)

Is that Correct? Wouldn't it be iB not B?

Though it looks like you do have the correct formatting, e.g: 32 KB = -i32 KiB

I'm so geeky I got really excited about making this signature in SVG until it occurred to me HTML would obviously be turned off ¬_¬'