lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <soyssk73kxv4njvwmfq635q4wolfjhgprlq3mfvxnciurzxhsh@g72tril7ys2k>
Date: Wed, 6 Nov 2024 18:44:08 +0100
From: Alejandro Colomar <alx@...nel.org>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Kuniyuki Iwashima <kuniyu@...zon.com>, alexhenrie24@...il.com, 
	branden@...ian.org, linux-man@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] rtnetlink.7: Document struct ifa_cacheinfo

Hi Stephen,

On Wed, Nov 06, 2024 at 09:18:01AM GMT, Stephen Hemminger wrote:
> On Tue, 5 Nov 2024 12:33:48 +0100
> Alejandro Colomar <alx@...nel.org> wrote:
> 
> > Hi Alex, Kuniyuki, Branden,
> > 
> > On Mon, Nov 04, 2024 at 09:53:38PM GMT, Kuniyuki Iwashima wrote:
> > > From: Alex Henrie <alexhenrie24@...il.com>
> > > Date: Mon,  4 Nov 2024 21:14:20 -0700  
> > > > struct ifa_cacheinfo contains the address's creation time, update time,
> > > > preferred lifetime, and valid lifetime. See  
> > 
> > We use two spaces after period (the correct amount).  :)
> 
> Double spacing after period is a leftover from using typewriters.

That's a lie that modern style guides repeat believing that repeating it
will eventually make it true (as if that were possible).

The origin is much older, and ancient (pre-typewriter) books already
used different space lengths for after period.

The true reason why the 2-space tradition was replaced by the 1-space
modern rule is that editorials started hiring incompetent people, and
it seems it was hard for that incompetent people to decide if one space
or two spaces were appropriate at a given place, so they would get it
wrong.  To avoid being embarrased by frequent spacing typos, instead of
hiring competent people (which would have been expensive), they simply
changed the rules to accomodate for those incompetent ones, and told
them to unconditionally use 1 space always.  That also reduces the time
they had to think about the number of spaces being used, so they became
more efficient.

But that removes information from the text.  If a sentence ends in some
initials, it's hard to distinguish if it's the end of a sentence, or if
the sentence continues and the dot is just for the initials.  It seems
the editorials just cared about generating text faster, and didn't care
at all about readers having more difficulty in reading what they wrote
(which just shows the low quality of what they produced).

Ironically enough, studies promoted by the defendants of the one-space
rule proof that two spaces result in more readable text.  They try to
write their conclusions as if not, but if you read enough in their
experiments, you realize how blind they are with their own experiments.

And also ironically, those one-space defendants say two-space tradition
is obsolete cruft from times where mono-spaced fonts were prevalent.
Guess what?  We here still live in a world were mono-spaced fonts are
the rule (anyone reading manual pages in a terminal here?) (I guess none
of us programs with proportional fonts, right?), so even if all those
lies were true (and they are not), in our reigns two-spaces should still
be the rule.

We had some discussion about this a few years ago, and we had links for
the claims I'm making, so I want to eventually recollect those links and
document it well for all contributors to see.

> Modern usage is single space after period.
> 
> https://www.grammarly.com/blog/punctuation-capitalization/spaces-after-period/
> 
> 	These days most contemporary style guides also recommend using a single space between sentences,
> 	including:
> 
> 	The Chicago Manual of Style
> 	The American Psychological Association (often referred to as “APA”)
> 	Microsoft Manual of Style
> 	The Gregg Reference Manual
> 	The Associated Press Stylebook

Paraphrasing the Linux kernel coding style...

	First off, I’d suggest printing out a copy of the Chicago Manual
	of Style, and NOT read it.  Burn it, it’s a great symbolic
	gesture.


Have a lovely night!
Alex


-- 
<https://www.alejandro-colomar.es/>

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ