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

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Most of the stuttering can easily be fixed by generating a PSO cache and compiling every shader before loading the game, it's up to the developer to set it up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!