9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: lucio@proxima.alt.za,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] devtrace release time
Date: Thu, 18 Dec 2008 17:08:53 +0900	[thread overview]
Message-ID: <140e7ec30812180008qad9b75madd55fad684d7730@mail.gmail.com> (raw)
In-Reply-To: <6487e3461bf190c64ebc357e9bb6998b@proxima.alt.za>

On Thu, Dec 18, 2008 at 12:52 PM,  <lucio@proxima.alt.za> wrote:
> Uriel is renowned for demanding tools to be released on principle,
> without him having any practical need for them.

 I don't see why uriel having a practical need for them or not is
relevant. I see the relevant question as "does /anyone/ in the
community have a practical need for the tool?".
 That's really hard to answer when the mere fact that the tool exists
is not readily available to the community (how DO we know about the
x86-64 kernel? I think everything I've heard about it has been via
uriel).

>  He lands up sounding
> like a peevish, ungrateful child who just wants more sweets even
> though his hands are already full.

 But unlike a child looking for sweets, uriel isn't complaining for
his own benefit:

> What could he possibly need with devtrace anyway?

 Exactly! His desire is not to get the code for himself, but for the
code to be available for anyone who does want to use/debug/develop it.

 Yes, uriel's manner is abrasive, and it gets old listening to him
make the same complaints over and over. But it boils down to this:
when uriel perceives an inhibitor to plan 9's growth and development,
uriel raises his voice (because no one else will!). Maybe he's not
always right, and maybe his righteous attitude makes him hard to
reason with, but his heart is in the right place.

-sqweek, wishing we could all just get along

PS. Congrats on the release, John/Ron/Aki!



  parent reply	other threads:[~2008-12-18  8:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 19:36 john
2008-12-17 19:50 ` Uriel
2008-12-17 19:55   ` john
2008-12-17 20:08     ` Uriel
2008-12-17 22:07       ` ron minnich
2008-12-17 22:18         ` Eric Van Hensbergen
2008-12-17 23:34         ` Devon H. O'Dell
2008-12-18  3:52         ` lucio
2008-12-18  4:38           ` Uriel
2008-12-18  4:55           ` john
2008-12-18  4:59             ` Nathaniel W Filardo
2008-12-18  5:04               ` john
2008-12-18  5:08                 ` Uriel
2008-12-18  6:10               ` lucio
2008-12-18  8:08           ` sqweek [this message]
2008-12-18  8:47             ` lucio
2008-12-18 11:33               ` sqweek
2008-12-18 11:42                 ` lucio
2008-12-18 13:26                   ` erik quanstrom
2008-12-18 16:30                   ` sqweek
2008-12-18 16:54                     ` Steve Simon
2008-12-18 17:02                       ` lucio
2008-12-18 18:06                       ` sqweek
2008-12-18 18:32                         ` erik quanstrom
2008-12-18 19:06                     ` C H Forsyth
2008-12-18 22:50                       ` sqweek
2008-12-18 23:59                         ` ron minnich
2008-12-18 16:42               ` ron minnich
2008-12-18 16:59                 ` lucio
2008-12-18 16:25             ` ron minnich

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=140e7ec30812180008qad9b75madd55fad684d7730@mail.gmail.com \
    --to=sqweek@gmail.com \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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;
as well as URLs for NNTP newsgroup(s).