Moreover, "Mebibyte", "Kibibyte", etc, sound (and look) _incredibly
stupid_. I'm sure as hell not going to use them, for that reason alone.
And if nobody uses them, they will go away.
This is why it's a good idea for standards authorities to stick to
standardizing common practice, instead of attempting to invent their
own. When they attempt to do the latter, then more often than not
simply screw it up royally, and then we're left with the annoyance of
having to ignore a "standard".
Exactly.
Of course, the Oxford English Dictionary do just that.
One finds that technical society only ignores standards in exceptional
cases. When they have very good reason to.
that is how language develops and evolves.
There is no historical precedent for standards "authorities",
redefining technical terms against the established ways society uses
them. They do not have that authority anyway.
There are certain expressions that sound really stupid, and so people
do not use them. That is not silly/immature. An old fellow once told
me he "had a fanny". (a fanny is of course a "woman hole"). What he
meant was he had a funny thing, a strange problem, with a set of
(accountancy) accounts. That expression was news to me.
People obviously did not like using that expression, it died out,
language evolved. And of course female accountants have never
casually strolled out of their offices and declared that they have a
penis.
There are organisations that want to change the way we spell , to make
it more intuitive, easier for people that cannot spell. No doubt, with
such a plan, they have written "standards" covering all commonly used
words. But those standards are not going to be adopted.
For better or worse, we do not talk like shakespeare anymore. Society
changed it. People at the Oxford Dictionary scramble to keep up to
date with society, and they write a good dictionary.
Let mathematical society use its technical terms the way it wants.
And computer techies use theirs.
Societies decide.
In the old days, of assembly language programming, most people doing
things with computers, computer scientists and others, were
mathematicians or people with a strong mathematical streak. And they
still said Megabyte knowing they meant 2^20, and Kilobyte - 2^10
e.t.c.. For obvious reasons.
<snip>
The people writing this standard are ants and mice compared to all the
old assembly language programmers. That is their place in society.
Any "body" can write a standard like this!! We have not heard much
more than a squeak out of these people. It is not to be compared to
a standard for a technology, written by those that invented the
technology. Those people are not ants. Neither are those that wrote
the original mathematical SI notation standard prefixes. And sensibly
these standards have been widely adopted. But not completely.
I hate to defend marketers, but the fact is that if they are not
technical, and they have to deal with end users who are not technical,
and they are trying to sell to end users and business managers. And
not make them run in fear. So they use terms in a non technical,
liberal way, and they use terms that will catch on to other idiot non
technical people, end users. Nobody has put marketers or end users in
prison - unfortunately. But they are often pushed away by technical
society. Often unfortunately, they are not pushed away, when (bad)
technical people have to work with them, they humour them or they make
compromises.
If one wants to talk about standards bodies having "AUTHORITY".
Ethernet inventors have authority to define words related to their
technology. In their standards specifications.
The differences are obvious. They are completely different kinds of
standard.
One cannot compare ignoring this standard with ignoring that standard.
Not all standards are equal.
RFCs do not have authority, though they are widely accepted. They also
only say they are "guidelines". And also, they are not
specifications.. (unfortunately, in the case of RFCs, one reason why
they call themselves guidelines, is because they know they are crap!!
And as they themselves say , the terms are only defined the way the
RFC they are in "defines", err, uses, them).
<snip>