public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Colomar <alx.manpages@gmail.com>
To: Stefan Puiu <stefan.puiu@gmail.com>,
	coreutils@gnu.org,
	Debian Install System Team <debian-boot@lists.debian.org>
Cc: Brian Inglis <Brian.Inglis@shaw.ca>,
	Linux Man Pages <linux-man@vger.kernel.org>,
	1031275@bugs.debian.org
Subject: Re: [PATCH v3 1/6] man2/: use IEC or ISO multiples to clarify long numeric digit strings
Date: Mon, 20 Feb 2023 16:35:06 +0100	[thread overview]
Message-ID: <2c23a82f-4392-2e4d-7aaa-2e2d17264738@gmail.com> (raw)
In-Reply-To: <CACKs7VCWsF+Pvso-H0VhTr2HFWUBs5JJ=m6uCJ7yB_FPY9g5Bg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2748 bytes --]

On 2/20/23 15:29, Stefan Puiu wrote:
> Hi Alex,

Hi Stefan,

>> 4 KiB is not that much better than 4096, since 4096 is easy to read.
>> For higher numbers such as 33554432, it becomes more important to use 32 KiB.
>> For consistency, using 4 KiB seems reasonable.
> 
> How about using KiB / MiB over a certain number of digits? It seems
> excessive to use them everywhere.

We might do that.  So far, I prefer having the patches change 
everything, and then we can later discuss about discarding part of them.

> 
> Also, for the record, I had no idea what KiB / MiB means and how it's
> different from KB/MB until this discussion. I googled it before
> writing this reply, and found this among the first hits:
> https://ux.stackexchange.com/a/13850.

That answer was written more than a decade ago.  These days, binary 
prefixes are more common.  In fact, I'd say most GNU/Linux commands 
respect them (an important exception being GNU coreutils (for example 
ls(1)).  But many programs use prefixes accurately, such as fdisk(8).

In the Linux man-pages we have units(7), which documents these.  Maybe 
that page should be more known.

BTW, that answer is inaccurate (at least today): drive manufacturers 
have the distinction pretty clear, and use it precisely (with lawsuits 
won thanks to this); they use metric prefixes, because they mean it. 
They can sell you 1 TB instead of 1 TiB, and most people won't even 
know, but those who know, will know that 1 TB is 1'000'000'000'000 B, 
which is what you get.  They have no incentives to sell 1 TiB drives, 
because they are visually almost the same, but there's around 9.95% more 
bytes, so it's more expensive to produce.  It's not worth it for them.

> 
> I would say making the docs easy to understand for users is more
> important than adhering to some specs users might not be familiar
> with.

Well, using MiB prompts readers to use their search engine to learn what 
that is (that's how I learnt it the first time; and that's what one does 
when reading a book and finding a new word).  I think that shouldn't be 
considered an impediment, but an opportunity to learn something new.

Once you know the difference, you appreciate the preciseness.  I hate 
when I see some software that uses the metric prefixes for meaning 
binary multipliers.  I also hate software that operates on bytes, when 
you almost always want binary multipliers but only have metric 
multipliers (hey partman, I mean you!).  I reported a bug to the Debian 
installer recently because it's very painful to partition a drive from it.

Cheers,

Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-20 15:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 20:15 [PATCH v3 0/6] man2/: use C digit separators, IEC, or ISO multiples to clarify long numeric digit strings Brian Inglis
2023-02-15 20:17 ` Brian Inglis
2023-02-15 20:17 ` [PATCH v3 1/6] man2/: use IEC " Brian Inglis
2023-02-15 21:05   ` Alejandro Colomar
2023-02-16 21:06   ` Stefan Puiu
2023-02-16 23:01     ` Alejandro Colomar
2023-02-16 23:40       ` Brian Inglis
2023-02-16 23:51         ` Alejandro Colomar
2023-02-17 14:05       ` Stefan Puiu
2023-02-19 21:10         ` Alejandro Colomar
2023-02-19 21:12           ` Alejandro Colomar
2023-02-20 14:29           ` Stefan Puiu
2023-02-20 15:35             ` Alex Colomar [this message]
2023-02-21 17:00               ` Rob Landley
2023-02-22  1:34                 ` Alex Colomar
2023-02-22 22:18                   ` Rob Landley
2023-02-24  1:05                     ` Alex Colomar
2023-02-16 21:40   ` Jakub Wilk
2023-02-15 20:17 ` [PATCH v3 2/6] man2/keyctl.2: use IEC or ISO multiples or add C digit separators " Brian Inglis
2023-02-15 21:06   ` Alejandro Colomar
2023-02-15 20:17 ` [PATCH v3 3/6] man2/: add C digit separators to clarify POSIX feature release dates Brian Inglis
2023-02-15 21:08   ` Alejandro Colomar
2023-02-16 21:11   ` Stefan Puiu
2023-02-16 23:04     ` Alejandro Colomar
2023-02-17 14:16       ` Stefan Puiu
2023-02-15 20:17 ` [PATCH v3 4/6] man2/select.2: add C digit separators to clarify POSIX feature release dates or use IEC or ISO multiples to clarify long numeric digit strings Brian Inglis
2023-02-15 21:09   ` Alejandro Colomar
2023-02-15 20:17 ` [PATCH v3 5/6] man2/chmod.2: add C digit separators to clarify POSIX feature release dates and " Brian Inglis
2023-02-15 21:10   ` Alejandro Colomar
2023-02-18 17:42     ` Tom Schwindl
2023-02-18 18:08       ` G. Branden Robinson
2023-02-18 18:31         ` Tom Schwindl
2023-02-18 19:03           ` G. Branden Robinson
2023-02-18 23:32             ` Brian Inglis
2023-02-19 11:50             ` ADA and base prefix for numbers Alejandro Colomar
2023-02-18 18:41       ` [PATCH v3 5/6] man2/chmod.2: add C digit separators to clarify POSIX feature release dates and long numeric digit strings Brian Inglis
2023-02-15 20:17 ` [PATCH v3 6/6] man2/: add C digit separators to clarify " Brian Inglis
2023-02-15 21:14   ` Alejandro Colomar
2023-02-15 22:51 ` [PATCH v3 0/6] man2/: use C digit separators, IEC, or ISO multiples " Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c23a82f-4392-2e4d-7aaa-2e2d17264738@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=1031275@bugs.debian.org \
    --cc=Brian.Inglis@shaw.ca \
    --cc=coreutils@gnu.org \
    --cc=debian-boot@lists.debian.org \
    --cc=linux-man@vger.kernel.org \
    --cc=stefan.puiu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox