public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	apw@canonical.com
Subject: Re: Please fix or revert: [PATCH] checkpatch: add --strict tests for braces, comments and casts
Date: Wed, 25 Apr 2012 10:33:13 +0200	[thread overview]
Message-ID: <20120425083313.GA20853@gmail.com> (raw)
In-Reply-To: <20120416.170004.2154403807488537042.davem@davemloft.net>


* David Miller <davem@davemloft.net> wrote:

> From: Ingo Molnar <mingo@kernel.org>
> Date: Mon, 16 Apr 2012 22:34:51 +0200
> 
> > 
> > * Ingo Molnar <mingo@kernel.org> wrote:
> > 
> >>     If you don't "see" it as ugly it's simply because your brain
> >>     is not wired up to see 3D/2D geometry as a significant
> >>     source of information. A significant portion (I'd 
> >>     guesstimate a narrow majority) of kernel hackers *does* see
> >>     2D/3D layout details in code and finds inconsistencies in 
> >>     them counterproductive.
> >> 
> >>     ( It's roughly the same distinction that makes some people
> >>       love the typographic layout of the iPhone/iPad while 
> >>       others consider it unnecessary bling. )
> > 
> > Another example are the recent Google+ layout changes. Those who 
> > don't see 2D details found it an unnecessary waste of screen 
> > real estate.
> > 
> > To me and many others the new layout, while sparser, is actually 
> > noticeably less taxing to read, because information is 
> > structured in such a "geometrically obvious" way.
> 
> I guess us visual retards will have to find a new web site to 
> use then, thanks for the lesson Ingo.

All I'm trying to point out is that it's a visual conflict that 
exists which probably has genetic origins.

For you it's too much whitespace, for me (and apparently Linus) 
the lack of it results in harder to read patterns of code due to 
missing geometric symmetry clues.

Since I don't have your brain and your eyes I cannot know 
exactly how bad the extra whitespaces are for you - and you 
probably don't know how bad the lack of symmetry is for me and 
others.

So I did not intend to make any judgement about it one way or 
another, but I guessed that a bit more vertical size is probably 
less taxing than less structure - but I'm obviously biased. If 
it's really bad for you we can still reconsider.

( I suspect it would be pretty hard but not impossible to
  construct an objective readability test to settle similar 
  issues scientifically and create an 'ideal' coding style based 
  on objective rules alone, eliminating subjective 'taste'. )

Thanks,

	Ingo

  parent reply	other threads:[~2012-04-25  8:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  9:17 Please fix or revert: [PATCH] checkpatch: add --strict tests for braces, comments and casts Ingo Molnar
2012-04-16 18:27 ` David Miller
2012-04-16 19:09   ` Linus Torvalds
2012-04-16 19:13     ` David Miller
2012-04-16 20:26   ` Ingo Molnar
2012-04-16 20:34     ` Joe Perches
2012-04-16 20:34     ` Ingo Molnar
2012-04-16 21:00       ` David Miller
2012-04-17  3:30         ` Steven Rostedt
2012-04-25  8:33         ` Ingo Molnar [this message]
2012-04-16 20:58     ` David Miller
2012-04-25  8:42       ` Ingo Molnar
2012-04-16 19:44 ` Randy Dunlap
2012-04-16 19:32   ` [PATCH] checkpatch: revert --strict test for net/ and drivers/net block comment style Joe Perches
2012-04-16 19:35   ` Joe Perches
2012-04-16 20:28     ` Ingo Molnar
2012-04-16 20:33       ` Linus Torvalds
2012-04-17 10:07         ` Ingo Molnar
2012-04-25 22:42           ` Joe Perches

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=20120425083313.GA20853@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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