https://bugs.kde.org/show_bug.cgi?id=364321
--- Comment #14 from Hector Martin <hec...@marcansoft.com> --- Of course JEDEC would use the binary definition; their entire business is basically RAM and Flash specifications. They are basically the only organization with a reason to prefer binary powers of 2, as they define specs for the only hardware where that still is useful in any way :-) But yes, this should be configurable; I don't think we're ever going to convince everyone of our way being the Right Way and we shouldn't need to. One of the reasons to use KDE is its configurability. That said, ever since people started talking calling 1440 KiB floppies "1.44 MB" (which is incorrect regardless of what definition of MB you use) the problem with binary units has been evident. Nobody can do power of two math in their head properly. The only significant argument for binary units is tradition/historical reasons (or being compatible with Windows). The thing is, they made sense when storage capacities were small enough that they were small multiples of the unit size (i.e. sector size, usually a small power of 2) since then you end up with "nice" numbers in binary units. But once your capacity is more than 4 or 5 orders of magnitude larger than the base unit (>1 prefix), this stops making any sense because capacities are not themselves powers of two and you're not going to get nice round numbers no matter what. I'm not going to make a big deal about binary units being the default if it ends up like that, but I do think the average user is better served by power of 10 prefixes (and those who prefer power of two prefixes can definitely go and change the setting). Either way it should be a setting. -- You are receiving this mail because: You are watching all bug changes.
