At 04:47 AM 12/22/01 -0600, Phil Howard wrote:
>I can understand your point about not jumping into something that will turn
>out (possibly) to be a big flop and cause new confusion. However, I'd like
>to point out that any new idea will _never_ become adopted if everyone takes
>the position of "I'm not going to do it until most everyone else does first".
Let's make clear what we are talking about. We are talking about making
the change to the one place that will be exposed to the non-technical user,
but not anywhere else (internal documentation, comments to the source code,
output from /proc, userland programs). In other words, the absolutely
worst place in the GNU/Linux system to introduce new and confusing usage
that is not widely used.
Get the hint? Let's change usage FIRST in the places that don't have the
exposure of a Help File to the general public, THEN consider making the
change once the users (technical and non-) have had a chance to voice their
opinion.
I don't know about y'all, but my non-technical clients have enough problems
with the historical abbreviations and terminology without being thrown this
curve. Unless you can get the business community to cry out for the change
(so that BSD, what's left of BeOS, and Microsoft make the change) this is a
Bad Idea(tm).
Look, I agree that there is significant merit to KiB et. al., but the
marketplace has not always selected that which is best. That's the nature
of the marketplace.
Stephen Satchell
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:27 EST