Another controversial change for Ubuntu 10.04: File size policy


Recommended Posts

Kilo means 10^3 everywhere, always and forever. It's an international standard clearly defined to be for powers of 10.

The IEC resolution that defined that was only passed in 1999. Those of us who have been using computers since the early 80's (or longer) know better.

Because it works better for digital calculations. Ask yourself why 1Byte has 8 bits? For the same reason, having 9bits you wouldn't be able to divide by 2, and 8 is a better choice than 10 because it's 2^3, while 10 is not a power of 2. 1024 is 2^10, while 1000 is not a power of 2 which complicates the ability of processors to calculate data.

Everything is in their right place, there is no use to put decimal system in computers because the hardware itself will never use it.

while dividing by a power of 2 is a bitshift operation and dividing by a power of 10 is not (yes i've programmed both RISC and CISC processors), and thus you are right about speed. Do you really think that expressing file size according to standards will have an impact on your computer performance?

Unless you're from a country that actually use base 10 for their measurements, ie, not inches, feet, yards, stone, puntd and whatever, you are not allowed to complain about kilobytes being 1024 bytes. :p

Unless you're from a country that actually use base 10 for their measurements, ie, not inches, feet, yards, stone, puntd and whatever, you are not allowed to complain about kilobytes being 1024 bytes. :p

you mean like every country in the world except the USA :p

while dividing by a power of 2 is a bitshift operation and dividing by a power of 10 is not (yes i've programmed both RISC and CISC processors), and thus you are right about speed. Do you really think that expressing file size according to standards will have an impact on your computer performance?

Obviously not, I'm just explaining that what we've used as 1KiB = 1024 Bit is correct and not wrong.

The IEC resolution that defined that was only passed in 1999. Those of us who have been using computers since the early 80's (or longer) know better.

kilo is taken from the metric system which has it's origins around 400 years ago. The prefix 'kilo' itself derives form a similar-sounding greek word meaning thousand.

Y'know, it's hardly an earth shattering change.

It's not preventing the 1,024 method of calculation from existing, just correcting the terminology used ... and it's a change that's long overdue. Just because it's "always been wrong" doesn't mean it has to stay that way.

Y'know, it's hardly an earth shattering change.

It's not preventing the 1,024 method of calculation from existing, just correcting the terminology used ... and it's a change that's long overdue. Just because it's "always been wrong" doesn't mean it has to stay that way.

(Y)

Good for Ubuntu (and I don't say that often :p)

Why change something after so many years? People need to learn computers work on the base2 structure and not base10.

Do average users really need to know that? In order to send emails, use Facebook and what-not?

Why change something after so many years? People need to learn computers work on the base2 structure and not base10.

The issue is that the unit terminology is wrong. k, M, etc. are specifically "thousands". It's been used incorrectly in computing.

That's why there is the KiB, MiB terminology for "1,024" systems.

Opposing this is silly, why stick with a confusing, archaic system (like the US hanging on to imperial measurements) when a sensible alternative was standardised a decade ago! Whilst you may be able to tell the difference between 1kB and 1KB, this breaks down for megabytes/mebibytes and all units above. It is simply confusing trying to decipher units of measurements and can introduce huge miscalculations.

For usability perhaps Ubuntu should display both, and educate its users if they don't understand, rather than dumb down for them.

Stone is used in the UK, but yeah. They tried to switch us over in the 70s and we told them to go jump off a cliff.

Well officially we use the metric system, all weights in supermarkets etc. are metric.

Stone is used in the UK, but yeah. They tried to switch us over in the 70s and we told them to go jump off a cliff.

No "we" didn't. Schools have taught primarily metric for decades. Our money was switched to decimal (basically metric) in the very decade you speak of.

Stone is just used for convenience, mainly because older people grew up with it and continue to use it.

Not something that will largely affect me. Frankly I dont care. With harddrives in the TB range and probably larger coming in the next few years, should we really complain over a few bytes (giga, kilo, mega, whatever)?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
    • It is clear from this aricle that "Time Is On My Side" no matter which direction it is flowing., https://noai.duckduckgo.com/?i...m%2Fwatch%3Fv%3DsEj8lUx0gwY
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      578
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!