this post was submitted on 24 Aug 2023
111 points (95.9% liked)

Android

17677 readers
25 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
 

cross-posted from !samsung@lemdro.id

top 22 comments
sorted by: hot top controversial new old
[–] ElPussyKangaroo@lemdro.id 26 points 1 year ago (1 children)

Wow. Samsung Innovation is truly big!

[–] ijeff@lemdro.id 16 points 1 year ago

But how big in mebibytes?

[–] Steve@communick.news 22 points 1 year ago (1 children)

Those are different systems, though, with gigabytes measured in powers of 1,024 and gibibytes in powers of 1,000.

They got those backwards! The whole concept hinges on this, and they flipped the values! Sometimes I love tech writers.

[–] ijeff@lemdro.id 11 points 1 year ago

Backward indeed! I've always found the Wikipedia chart helpful.

[–] JoelJ@lemmy.world 12 points 1 year ago (1 children)

Maybe to avoid confusion, they should just display units in GB instead of GiB? Or just display both

[–] Psythik@lemm.ee 11 points 1 year ago* (last edited 1 year ago) (3 children)

I still don't understand the difference. GB sometimes means 1024 MB, and sometimes it means 1000. But then also sometimes it also means ether 1000 MiB or 1024 MiB, depending on who's saying it.

The whole "iB" thing was supposed to clear up confusion but it only makes it worse. I don't understand why we can't just make 1GB = 1024 MB, ditch the silly "iB" nonsense, and then just call it a day.

I blame hard drive manufacturers. They're the ones who started this whole 1GB = 1000MB bullshit.

[–] JoeClu@lemmy.world 8 points 1 year ago* (last edited 1 year ago) (2 children)

I agree with you. A long time ago, those of us "in the know" techies could parse the difference like it was a native language. When talking anything but computers, it was always the SI of 1000. When talking about computers, it was always 1024.

I think the masses were confused and the SI purists felt their SI prefixes were being corrupted. So they made a distinction/standard between binary numbering system prefixes and decimal numbering system prefixes.

I hate it. Feels wrong because I'm old and set in my ways. People like me are confused because we still use the old nomenclature, and when someone else uses the old nomenclature (when talking about computers), it's ambiguous to us because we don't know which numbering system they are using (e.g., binary as opposed to decimal). I still have to ask and half say binary and half say decimal.

I suppose if they're teaching it in high school and college it'll become native soon enough, if it hasn't already with the next generations.

[–] LaggyKar@programming.dev 3 points 1 year ago* (last edited 1 year ago) (1 children)

When talking about computers, it was always 1024.

No. Hard drive sizes are always given with decimal prefixes. Always have been.

[–] JoeClu@lemmy.world 4 points 1 year ago

I wasn't talking about HDD sizes, but I know the person to which I was replying was talking about HDD's specifically. I shou,d have clarified I was talking in more general terms (CPU RAM, NVM sizes, etc.)

I remember being miffed about the advertising of the HDD sizes. So I think you are correct there. Wish I could go back to the mid 80's and do some research on my old HDDs and floppies. I honestly just can't remember, so thank you.

I hate the new prefixes, not just because they aren't the older nomenclature, but because they feel ridiculous to speak out loud. If a less silly sounding prefix was chosen, I probably wouldn't be tainted about it.

[–] tal@kbin.social 1 points 1 year ago* (last edited 1 year ago) (1 children)

When talking about computers, it was always 1024.

The problem is that each time you go up another unit, the binary and decimal units diverge further.

It rarely mattered much when you're talking about the difference between kibibytes and kilobytes. In the 1980s, with the size of memory and storage available, the difference was minor, so using the decimal unit was a pretty good approximation for most things. But as we deal with larger amounts of data, the error becomes more-significant.

Decimal unit Binary unit Divergence
kilobyte (kB) kibiyte (kiB) 2.4%
megabyte (MB) mebibyte (MiB) 4.9%
gigabyte (GB) gibibyte (GiB) 7.4%
terabyte (TB) tebibyte (TiB) 10.0%
petabyte (PB) pebibyte (PiB) 12.6%
exabyte (EB) exbibyte (EiB) 15.3%
[–] JoeClu@lemmy.world 1 points 1 year ago

This is exactly right. Divergence was small when sizes were small. Good point.

[–] LaggyKar@programming.dev -2 points 1 year ago* (last edited 1 year ago)

I don't understand why we can't just make 1 G=1 G, ditch the silly contex-sensitive-prefixes nonsense, and call it a day.

I blame memory manufacturers. They're the ones who started this whole 1 GB sometimes= 1024 MB bullshit.

[–] ipha@lemm.ee 7 points 1 year ago

Wait, they're just lying in a different place now.

[–] somegadgetguy@lemdro.id 5 points 1 year ago* (last edited 5 months ago)
[–] LaughingFox@lemmy.world 4 points 1 year ago (2 children)

Iook I'm not a tech person, I always thought 1 gig was 1024 megabytes?

What is a GiB? I've seen it but always wondered.

[–] cjf@feddit.uk 12 points 1 year ago* (last edited 1 year ago) (2 children)

GB is metric and it’s easy for us to remember. E.g. 1000 bytes = 1 Kilobyte, 1000 kilobytes = megabyte and so on.

GiB is the binary value. In binary, you have to work in powers of 2. That is… the values double every time (2, 4, 8, 16, 32, 64 and so on…). 1024 bytes = 1 KiB, 1024 KiB = 1 MiB

Since computers work in binary, and 1000 isn’t a number that’s easy to deal with in binary, we use the closest value available to us, 1024. In fact, back in the days when people were only concerned about KBs, they would say that 1000 KB = 1024 KiB.

Of course, we’re now working with TBs rather than KBs. Everything ramps up including the amount of “missing” space an OS reports on a hard drive.

I know windows tries to be helpful and shows you the value of a drive in GB, rather than its GiB value. Ever wonder why a 1TB hard drive appears as ~931GBs? This is why. Other OSes tend to show you the GiB value since that’s generally a lot more accurate.

[–] Pxtl@lemmy.ca 9 points 1 year ago* (last edited 1 year ago)

An important thing to note about this is that as we go up exponentially the error between GiBs and GBs increases. A kiB is only 2% more than a kB, but a TiB is 10% more than a TB. So using them interchangeably is increasingly misleading.

Also, there are many cases in computers where it doesn't really make sense to fuss about binary. Like, an HDD is a spinning piece of metal, the number of bits it can store has no binary constraint.

Fun fact: the old 3.5" floppies that were marketed as 1.44 MB were neither 1.44MiBs nor 1.44 MBs, but some weird hybrid mash-up unit.

[–] FooBarrington@lemmy.world 4 points 1 year ago

To expand on this: people sometimes use SI prefixes to refer to 1024 units, but it's just wrong. A kilometer is 1000 meters, a kilogram is 1000 grams, and so on. If we were to re-define these prefixes for specific disciplines things get much more complicated very quickly.

[–] skullgiver@popplesburger.hilciferous.nl 3 points 1 year ago* (last edited 11 months ago) (1 children)

[This comment has been deleted by an automated system]

[–] Alonely0@mastodon.social 0 points 1 year ago (1 children)

@skullgiver @LaughingFox It's not programmer laziness at all, RAM modules' size has to be of a power of 2 on most platforms because of various assumptions the CPU makes in memory alignment and memory bulk reads for performance reasons. Processors don't interact directly with the flash dies, so it's fine for them to be of the size they feel like provided the controller knows what it's doing.

[–] skullgiver@popplesburger.hilciferous.nl 1 points 1 year ago* (last edited 11 months ago)

[This comment has been deleted by an automated system]