9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Colors and other fun
Date: Wed, 27 Jun 2007 11:26:21 -0700	[thread overview]
Message-ID: <20070627182621.C14B05B3B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 27 Jun 2007 08:07:19 PDT." <7359f0490706270807ia34da8bl408c6042474637b4@mail.gmail.com>

> It's more than that. Philosophically, I believe the designer's goal involves
> making decisions for the user. If the decisions are good, it's a good design
> and the user is content.  I do not believe it's the designer's goal to defer
> everything to the user.  As a bonus, making decisions early tends to
> simplify the design. This is why there are no stty modes or resource
> files in Plan 9.
>
> And why there are no 'dot files', although that issue also involves the
> avoidance of dot files filling up your home directory silently and slowing
> down every command that reads the most important directory in your
> world for the sake of customizability. A $USER/lib directory is a
> much sounder place to put such things.
>
> On a related note, I see no merit whatsoever in separating 'mechanism'
> from 'policy'. If the best design involves conflating them, go for it.
>
> -rob

Since you bring up design issues I have to ask! Plan9
graphics are limited to 2D and I have long wondered if
stopping there was by design (and lack of need) or because
you couldn't come up with a satisfactory 3D design.  In any
case, how you would you go about designing a 3D graphics
system?  Discussing ideas you have considered and thrown away
or ideas you have mused about but not taken further would be
quite interesting (at least to me).  Thanks!

-- bakul


  reply	other threads:[~2007-06-27 18:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  9:37 pavlovetsky
2007-06-27 10:08 ` Lucio De Re
2007-06-27 15:07   ` Rob Pike
2007-06-27 18:26     ` Bakul Shah [this message]
2007-06-27 18:35       ` Kris Maglione
2007-06-27 19:09         ` Bakul Shah
2007-06-27 19:24           ` David Leimbach
2007-06-27 19:39             ` Gabriel Diaz
2007-06-27 20:35               ` Bakul Shah
2007-06-27 21:20                 ` Jack Johnson
2007-06-29  2:16                   ` Bakul Shah
2007-06-27 19:51             ` Francisco J Ballesteros
2007-06-27 21:49               ` Jack Johnson
2007-07-02  8:55           ` Douglas A. Gwyn
2007-06-28  4:42     ` Anant Narayanan
2007-06-28  4:50       ` andrey mirtchovski
2007-06-28 17:30     ` Dave Eckhardt
2007-06-27 15:59 ` andrey mirtchovski
2007-06-27 16:23   ` Lorenzo Fernando Bivens de la Fuente
2007-06-27 17:55     ` Steve Simon
2007-06-27 18:03       ` erik quanstrom
2007-06-27 18:22         ` Rob Pike
2007-06-28 15:26         ` Steve Simon
2007-06-27 18:03       ` Kris Maglione
2007-06-27 18:59 Russ Cox
2007-06-27 19:13 ` Tim Wiess
2007-06-27 21:25 ` Charles Forsyth
2007-06-27 15:41   ` john
2007-06-27 21:56     ` erik quanstrom
2007-06-27 16:18       ` john
2007-06-27 22:06       ` Kris Maglione
2007-06-27 21:48 ` Markus Sonderegger

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=20070627182621.C14B05B3B@mail.bitblocks.com \
    --to=bakul+plan9@bitblocks.com \
    --cc=9fans@cse.psu.edu \
    /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).