Bytes do not. Bytes are made up of 8 bits, and bits are powers of 2. Neither of these facts have any relation to base10.
There is inevitable shoe-horning happening on either side of the argument.
If a new metric was to be introduced to provide for those who wish for "everything to be neat and tidy, excepting for the base unit", they should be the ones using a new term, while the rest of everyone continues using the incumbent one.
Overriding the commonly-accepted and widely-used term with a secondary meaning is a sub-optimum solution.
ISO and IEC standards defined a byte as 8 bits in the 1990s. But they also defined kilo and mega as powers of 10.
Powers of 2 were never used exclusively.
I've only made the correct claim that the logical continuance the employment of powers of 2 into units of scale was sufficiently widespread as to be considered convention, something those who created the standards you cite also readily acknowledge.
This sounds like a lame excuse for fraud.
Megabytes had a very specific meaning. Afterwards, for any random reason, that definition was turned upside down to mean about 5% less, and a terabyte to mean 10% less.
If you're going to buy a HD and you end up finding out it provides 100MB or 200MB less than advertised, you'd righteously feel defrauded.
That SD card you have? Base 10. Flash drive? Base 10. Hard drive? Base 10. SSD? Base 10. The only outlier here is RAM being base 2, but that’s because it’s in a grid, so 16 GB is easier to write than 17.18 GB.
I remember quite clearly at the time HDD's first started proliferating that many (intelligent) people were legitimately fooled and felt cheated.
In fact I wouldn't be at all surprised if there were lawsuits about it.
But like many things on this earth, sometimes the less logical and more confusing is what ends up being the accepted norm.
Why metric and imperial? Makes no sense, is confusing.
Why left side right side driving? Makes no sense, is confusing, causes accidents.
Bits and bytes had a standard, it was widespread, understood, logical and useful for those who most had to deal with them. Then one group went out, very likely seeing dollar signs, and decided to be different. They should be the ones adopting the incumbent, logical standard, not the rest of us adopting their less-useful new one, and definitely not ending up with two conflicting standards with a single lowercase letter separating them.
It is not logical to apply the same standard uniformly to everything regardless of its inherent characteristics. It's also not always the best course of action to blindly apply any rule without making exceptions. Bits and bytes already and inherently do not fit into a base10 paradigm, but a base2 paradigm.
Making an exception for the application of scale measurements for those units makes sense and worked perfectly fine, for decades. Confusion was created by those adopting a different standard, for dubious reasons.
The issue of consumer ignorance, which was largely created by storage manufacturers and later now embedded by Apple could have been easily and simply resolved with a tiny bit of education.
Indeed, at least through the 80's it often was.
It's actually not that hard for people to remember one four digit number to multiply or divide by, after they've had an explanation of why that's important and make sense. Building this into the UI along with explanation is also not difficult. Exactly the same as many other important things that are prone to being misunderstood are explained.
Everyone would be better off for it.
There is just none
In the standard metric system, Kilo / K = 1,000 units of something, Mega / M = 1,000,000 units of something (and down in scale also by dividing by 1,000). This applies for anything where the standard singular unit is 1, and assumes it can also be multiplied by, or divided into 1,000 pieces. For example: 1 gram equals 1,000 milligrams.
A computer however, does not have one base unit, but two: the bit and the byte. Neither are usefully divisible by 1,000. Conversely, multiplying the byte by 1,000 hides aspects of its structure that are essential to consider when building and programming a computer system. Considering that the metric system is about notating scale, and that there are issues in both directions of scale when applying the metric system to computers, it made sense to modify it slightly when doing so.
Luckily, there is a number very close to 1,000 that does usefully represent the inconvenient internal structure of a bit and a byte, at least at larger scales. That number is 1,024. Early computer scientists decided that for computers, Kilo / K = 1,024 bytes. It followed that Mega / M was 1,024 x 1,024 = 1,048,576 bytes, and so on. (1 GB = 1,024 x 1,024 x 1,024 = 1,073,741,824 bytes, or close to 1 billion bytes).
This "1,024 rule" for the computer application of metric system, matches the physical structure of computer memory exactly - and crucially, the parts of a computer that physically access memory - making it straightforward for programmers and hardware designers to work with and talk about.
---
And, from an alternate 1990's addendum to the previous:
It also means that when you see a Hard Drive advertised with a size of 240 MB, you can be sure that you are in fact getting 240 x 1,048,576 bytes of storage, or 251,658,240 bytes (well over 251 million bytes). That 251 million is, on appearance, quite a bit "more" than 240 MB is one of the bonuses of the "1,024 rule" for the computer metric system that can impact you directly. You're welcome!
Sticking with the first, widely-proliferated meaning we already had, which existed because of its usefulness, along with its direct honouring of the structure of what it was describing, is IMO the superior choice. This versus cementing the source of the confusion - the secondary meaning - even further by introducing it not only as an additional standard, but also as the de facto, nullifying years of text and understanding and rendering it inaccurate.
To me, that was, and is absolute madness.
Division by powers of 1000 ceased to be an expensive operation relative to user interaction a very very long time ago. And even back when it was, I am sure would the error have been in the order of 10% (as it is now with TB vs TiB), they absolutely would have taken the more expensive but more correct operation.
I just see no advantage in continuing to resist the unification of the meaning of prefixes. And where people prefer the old way for some nostalgic reason, just put the 'i' in there and you are good.