-1.
The conflict between niche "technically correct terminology even if no-one
actually uses these words" terms and "technically incorrect terminology but
everybody uses it anyway" should, in most cases, be won by the
technically-incorrect terminology. My favorite relevant examples of this
are the
In that case I believe it's more important to be understandable by our target
audience than to be technically correct. If we make the change we'll probably
get bug reports pointing out KiB as a typo.
I know that geeks love to feel smart by being more correct than the masses, so
I expect this ch
I'd be fine changing MB -> MiB in just docs wherever needed, and then not
using KB or MB at all because of their ambiguity. I've seen "KiB" and "MiB"
around before, but I've never seen "Mebi" before today.
On Monday, January 12, 2015 at 6:53:37 PM UTC-5, Markus Holtermann wrote:
>
> Hey folks,
See also 19348 and 8733.
https://code.djangoproject.com/ticket/19348
https://code.djangoproject.com/ticket/8733
My opinion hasn't really changed - my experience has been that Kibi and
Mebi are prefixes that nobody outside standards organisations give a damn
about.
In the example you provide (FIL
Hey folks,
I saw that the Django docs currently use file size units kB, MB, etc.
that refer to a multiple of 1000 (1000, 100 bytes respectively --
https://docs.djangoproject.com/en/dev/ref/settings/#file-upload-max-memory-size
). But the numbers actually are to the power of 1024. To remedy
inc
