Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: switch fileSizeTypes to binary prefixes #202

Open
ObbloFlorian opened this issue Jan 5, 2025 · 3 comments
Open

Suggestion: switch fileSizeTypes to binary prefixes #202

ObbloFlorian opened this issue Jan 5, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@ObbloFlorian
Copy link

ObbloFlorian commented Jan 5, 2025

Hello,

Currently, the fileSizeTypes are expressed with decimal prefixes (KB, MB, ...). The decimal prefixes mean "times 1000". But as you know, in computer science we most frequently manipulate binary, and "times 1024" is a more accurante information in most cases. In fact this discrepancy sometimes causes confusion for the users.

I suggest we update the fileSizeTypes to use the binary prefixes (KiB, MiB, ...) for a more accurate representation of file sizes in web apps. Some more information about these prefixes can be found on Wikipedia.

Note: I did some testing, and Google Translate appears to mistranslate the binary prefixes back to decimal prefixes in some (all?) languages, so if we choose to use binary prefixes, the translations will have to be done manually.

@melloware
Copy link
Member

melloware commented Jan 5, 2025

@ObbloFlorian I don't disagree that KiB, MiB are correct...but most users don't know these terms so I think PrimeTek chose the simpler KB and MB even if you divide by 1024 and its not "semantically" correct most users know what these means agree?

@ObbloFlorian
Copy link
Author

I do agree that most users are indeed more familiar with KB/MB. This is why my post is only a suggestion, I'd understand if the choice was made to keep them. But I figured, I might as well start a discussion on it.

I'm of the opinion that we should "push" KiB/MiB despite them not being well known, because I believe they are recognizable enough for laymen, and because I believe we should strive for accuracy.

Also I've encountered in the past some cases where I tried to upload a file somewhere that just so happened to be in the gray zone between x1000 and x1024, and met some strange behaviours in consequence. It's usually not a big deal, but it's an avoidable annoyance.

Again this is just a suggestion. Thanks for taking the time to consider it. I'll abide by whatever gets chosen in the end.

@melloware
Copy link
Member

No worries I will leave this suggestion open!

@melloware melloware added question Further information is requested enhancement New feature or request and removed question Further information is requested labels Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants