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

    • Depends on what you need. Might be a bit clearer on what you plan to do with it. Sort of a waste if you get the newest and greatest, but don't know how to use it.
    • NTLite 2026.06.11200 by Razvan Serea NTLite is a Windows configuration tool that allows you to modify your existing Windows install or an image yet to be deployed, remove Windows components, configure and integrate, speed up the Windows deployment process. Reduce Windows footprint on your RAM and storage drive memory. Remove components of your choice, guarded by compatibility safety mechanisms, which speed up finding that sweet spot. Windows Unattended feature support, providing many commonly used options on a single page for easy setup. Easily integrate a single or multiple drivers, update or language packages. Package integration features smart sorting, enabling you to seamlessly add packages for integration and the tool will apply them in the appropriate order, keeping hotfix compatibility in check. One of the important new features of NTLite (compared to its predecessors) is the ability to modify an already installed the operating system, by removing unnecessary components. Supports Windows 11, 10, 8.1 and 7, x86 and x64, live and image. Server editions of the same versions, excluding support for component removals and feature configuration. ARM64 image support in the alpha stage. Does not support Checked/Debug, Embedded, IoT editions, nor Vista or XP. NTLite 2026.06.11200 changelog: New Secure Boot Migration support: Verification, certificate staging, and boot-manager/sector update across the Image, Updates, Apply, and Create-ISO pages (2023 CA migration, optional 2011 revocation, Anti-rollback, Boot sector choice etc) Secure Boot Host Readiness: Live host Secure Boot migration monitor and Servicing-task control Option under Image page - C:\Windows row, or load the host as the target - Updates - Secure Boot Image: 'Sort mounted images first' option for the image list in Menu-Settings UI: Hover description card for Components and Unattended pages, selectable text and quick access to Compatibility options Command line: Relay commands into the already-running instance Enables controlling already running NTLite via ntlite.exe Use /NewInstance to launch an additional instance using CLI operations (premium) UI: 'New instance' option via main menu instead of a secondary ntlite.exe prompt Apply: Hide individual Apply-page notes with a per-note dismiss (X), critical excluded Settings: 'Unsigned RDP file launch warnings' tweak (RDP client), bypassing the April 2026 security-update prompt on RDP connections Upgrade Image: Live OS and deployed image editing now unlocked on free/test licenses, same licensing as images Image: 'Recompress' option in manual dialog Remove Editions to shrink the WIM in one session Image: SWM part size set inline on the Apply page and image dialogs, split-size popup retired Image: Relative 'Last change' dates; editions grouped by build time to reduce noise Image: 'Forget - Missing' on the Edit-cache menu to mass drop entries whose folder is gone Components: Root groups reorganized - user-facing groups first, system/critical last Components: Show filter options to view components by Template or App-type, since Apps are now merged into groups Presets: Delete confirmation now lists the multi-selected preset names UI: Design update propagated to the rest of the tool UI: Filter and search match words in any order and partially, better results filtering Components Unattended: Input-locale language derives from the user locale, with an independent keyboard picker, enables combinations previously unavailable Unattended: Input-locale now allows for a user value override Unattended: Localization OOBE WinPE now can be copied with the new WinPE Copy OOBE localization toggle, enter locale settings once for both stages Updates: Downloader greys and locks updates the image already carries (hotfix and MSIX) Updates: Resume interrupted update downloads Command line: Many upgrades, see /?, now prints help to the console or redirected output UI-Translation: Finnish language added, also thanks for Chinese Traditional (Matt), French (tistou77), Italian (clarensio), Russian (RDS), Swedish (1FF), Vietnamese (Vu Anh Vu) Fix Components: Containers removal breaking Apps deployment Components: Microsoft Account had leftovers when Easy Migrate is kept Image: Export to an existing WIM improvements, Append renamed to Merge Image: Improved 26H1 live removal support Image: No more 'X:\ not accessible' popup for certain drives during image scan Presets: Manual image refresh picks up presets added/removed outside the app Tweaks: Disabled visual-effect animations no longer return after first logon on a new profile Tweaks: Live Visual Effects toggles (animations, drag full windows, font smoothing) now apply correctly Download: NTLite 2026.06.11200 | 20.5 MB (Free, paid upgrade available) Link: NTLite Home Page | NTLite Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Ah. La Fontana De Incontinentia ! Bella ! Bella !
    • Hi everyone, I'm planning a small network upgrade and was wondering how others prepare their networks for future needs. Do you usually invest in higher-speed switches and better cabling from the start, or do you upgrade only when necessary? I'd be interested in hearing what has worked well for you and any lessons you've learned over time. Thanks!
    • Greetings and welcome!!
  • Recent Achievements

    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
    • First Post
      carols23 earned a badge
      First Post
    • One Month Later
      Tom Willson earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      257
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      93
    5. 5
      macoman
      67
  • Tell a friend

    Love Neowin? Tell a friend!