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

    • Funny, but I didn't had the issue. All PC's at work are Dell and we had the culprit version of Support Assist for about 2 weeks until we got the new one. No problem at all. And for checking you can also use Dell Command Update, no need to search in windows settings. Just check the Upgrade History.
    • YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    • Apple are scared of their customers! They have built a brand over the years of "it just works out of the box", but that slows innovation. Samsung's master stroke was the Galaxy Ultra: "Let's cram everything into one handset, make it so stupid only real nerds will love it, some of the features will work, some won't, but the audience will have such a high tolerance they won't care". Apple has no such device and so they are constantly worrying these days about the fallout of creating a new experience that customers might not like. I know it is often cited the reason they don't build a touchscreen Mac Book is they don't want to cannibalise the the iPad market, but I think it's equally cold feet after the criticism Microsoft receive trying to make a touch compatible desktop OS
    • HandBrake 1.11.2 by Razvan Serea HandBrake is an open-source, GPL-licensed, multiplatform, multithreaded video transcoder, available for MacOS X, Linux and Windows. Handbrake can process most common multimedia files and any DVD or BluRay sources that do not contain any kind of copy protection. Here is a detailed breakdown of HandBrake’s features: Built-in Device Presets—Get started with HandBrake in seconds by choosing a profile optimized for your device, or choose a universal profile for standard or high quality conversions. Simple, easy, fast. For those that want more choice, tweak many basic and advanced options to improve your encodes. Supported Input Sources—Handbrake can process most common multimedia files and any DVD or Blu-ray sources that do not contain any kind of copy protection. Outputs: File Containers: .MP4(.M4V) and .MKV Video Encoders: H.265 (x265 and QuickSync), H.264(x264 and QuickSync), H.265 MPEG-4 and MPEG-2, VP8 and Theora Audio Encoders: AAC / HE-AAC, MP3, Flac, AC3, or Vorbis Audio Pass-thru: AC-3, E-AC3, DTS, DTS-HD, TrueHD, AAC and MP3 tracks Additional features: Title/ Chapter Selection Queue up Multiple Encodes Chapter Markers Subtitles (VobSub, Closed Captions CEA-608, SSA, SRT) Constant Quality or Average BitRate Video Encoding Support for VFR, CFR and VFR Video Filters—Deinterlacing, Decomb, Detelecine, Deblock, Grayscale, Cropping and Scaling Live Video Preview HandBrake 1.11.2 changelog: All platforms Video Fixed a crash that happened when doing a 2-pass lossless x265 encode Fixed a memory leak that happened when doing a 2-pass MPEG-4/MPEG-2/VP9/FFV1 encode Audio Updated the list of supported dithers and encoders combinations Fixed the Core Audio AAC encoder 7.1 channel layout Subtitles Fixed the VobSub palette creation in the MP4 container Build system Improved build system compatibility with older build tools Third-party libraries FFmpeg 8.0.2 (decoding and filters) SVT-AV1 4.1.0 (AV1 video encoding) Linux Added WebM MIME type to the list of the supported formats Mac Improved handling of unsupported presets Updated Sparkle automatic update library Windows Improved handling of unsupported presets Improved queue low space pause behaviour Fixed the automatic audio track name generation Fixed the summary description of HDR video Download: HandBrake 64-bit | Portable 64-bit | ~30.0 (Open Source) Download: HandBrake ARM64 | Portable Links: HandBrake Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • So, an article that has nothing to do with Windows 11, still gets Windows 11 in the title and a build number as the picture? Dell have a buggy build of Support Assist HP have UEFI settings that need unlocking for the secureboot cert upgrade to take place.
  • 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
      243
    3. 3
      Steven P.
      72
    4. 4
      neufuse
      67
    5. 5
      ATLien_0
      67
  • Tell a friend

    Love Neowin? Tell a friend!