GigglyBobble

Ha, good one! Got me interested, how the standards bodies handle something like that. Found this in the Wikipedia article for byte:

The unit symbol for the byte is specified in IEC 80000-13, IEEE 1541 and the Metric Interchange Format[10] as the upper-case character B.

In the International System of Quantities (ISQ), B is the symbol of the bel, a unit of logarithmic power ratio named after Alexander Graham Bell, creating a conflict with the IEC specification. However, little danger of confusion exists, because the bel is a rarely used unit. It is used primarily in its decadic fraction, the decibel (dB), for signal strength and sound pressure level measurements, while a unit for one-tenth of a byte, the decibyte, and other fractions, are only used in derived units, such as transmission rates.

Somewhat disappointing. “There’s a conflict but it’s fine”.

But there is also nothing contradictory or wrong with the unit MB.

And I didn’t say that. Admittedly, the constraint “If the image size is defined as binary” probably could’ve been expressed better (I’m not a native speaker). File sizes are usually calculated in binary units (at least by Windows and the Linux distros I know - even though Windows continues to claim those are megabytes and Linux adopted the standardized units) and I’d bet that’s the case for file.coffee, too.

Oh, well, I’m pretty sure we’re not really disagreeing anyway. So let’s conclude with the obligatory relevant xkcd.

No.

Where’s the contradiction? Yes, it’s just a different prefix but it results in a different number. What I meant to adress is that very often people write MB/megabytes (10⁶ = 1,000,000 bytes) but actually mean MiB/mebibytes (2²⁰ = 1,048,576 bytes). RAM vendors possibly most prominently.

Well, acshually, bit doesn’t have a metric symbol and ‘b’ is defined as barn. So Mb would be a megabarn.

Edit: And to be even more nitpicking: If the image size is defined as binary, it should be MiB (mebibyte) since “mega” is defined as base 10.

That and the other good thing: no distro will make decisions that are even in the ballpark of insanity of those by big tech corps.

I had an iPhone 12 for two weeks before I returned it. I tried to like it because, while you’re still in a corp walled garden and they cannot really be trusted, they so far are better than Google at least with regards to privacy.

However, there’s a list of stuff that got me too annoyed. Some examples:

• the stock keyboard is just garbage. All the infamous typos on social media come from iPhones because they choose to correct words that have already been written. You also cannot sensibly replace the stock keyboard because you cannot block a specific app’s data usage and keyboards are far too critical apps to grant internet access.
• stock apps are good overall (better than Android) but that means people don’t make replacements. The mail app could’ve been great but they choose to not support PGP and it’s practically impossible to set up.
• you cannot replace Safari completely, some apps still open it. Safari is crap because no way to install adblock.
• you still feel that iOS wasn’t developed as a multi-threading system. I had a few apps that wouldn’t correctly work while in background
• apps are far more expensive than for Android. Lots of subscription-based plans, more comparable to full-price PC software than mobile apps.
• no native file system access. Apps are sandboxed and handle their files themselves. I prefer to do that myself but no chance on iOS.
• the community is garbage. Every question or critcisim is the user’s fault. The Holy Corp does not make mistakes. Collective Stockholm syndrome.

I also ran into various bugs. I do on every platform but the “it just works” narrative is especially strong for Apple and it’s just not like their fans claim.