9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Theo Honohan <theo@ideaworks3d.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Laura's theme (Long) (Was: [9fans] I've got 4 student intern (undergraduates) here.)
Date: Mon, 11 Jun 2001 15:28:07 +0100	[thread overview]
Message-ID: <E159SQT-0005qe-00@starfruit.iw3d.co.uk> (raw)
In-Reply-To: <20010611081451.A8737@cackle.proxima.alt.za>

On Monday 11 June, Lucio De Re wrote ("Laura's theme (Long) (Was: [9fans] I've got 4 student intern (undergraduates) here.)"):
> 
> Without excluding myself from the criticism, the Plan 9 culture is
> inherently elitist, rather than evangelical.  I'm about to embark on a
> cross-host debugging session (Inferno, rather than Plan 9, I'm not
> sure how successful I'm likely to be) and only when confronted by this
> need, did I realise that Laura's question about impressing students
> should have been answered by a cross-host task, the more convoluted,
> the better.  No one else has proposed such an idea, and yet the main
> strength of the fileserver approach lies clearly in that quarter.

Absolutely!  Well said.  I spent several futile hours at the weekend
trying to articulate exactly that point.

If the students have encountered the pseudo-network-transparency of X11
or NFS, they'll immediately appreciate the advantages of the Plan 9
approach.  It's all about just presenting the three main design
principles listed in the overview paper.  Then, you show that the Plan 9
approach solves all of the same problems as X, ssh X-forwarding, NFS and
VNC, in a much cleaner way.  That should appeal to any CS student.  Then
you show how it goes way beyond that, allowing fine-grained cross-host
sharing of resources.  Russ's anecdote about Windows and ssh is a good
example: 
http://lists.cse.psu.edu/archives/9fans/2000-October/007937.html

Not everyone will immediately recognize the need for that kind of
contortion, but people who have developed software across multiple
machines, or have run their own small network of Linux boxes, will be
sent into transports of delight.

I'm less convinced that Acme is a good selling point; people are
unlikely to see a new editor or IDE and think "Oh, I want to change
editors!"  Habits are hard to break, and editors are a matter of
personal taste (as are mouse chords...)

Theo



  reply	other threads:[~2001-06-11 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11  5:13 [9fans] I've got 4 student intern (undergraduates) here okamoto
2001-06-11  6:14 ` Laura's theme (Long) (Was: [9fans] I've got 4 student intern (undergraduates) here.) Lucio De Re
2001-06-11 14:28   ` Theo Honohan [this message]
2001-06-11 21:18     ` [9fans] " Boyd Roberts
2001-06-11  8:10 ` [9fans] I've got 4 student intern (undergraduates) here Borja Marcos
2001-06-11 13:39   ` GL again (was Re: [9fans] I've got 4 student intern (undergraduates) here.) Theo Honohan
2001-06-11  9:06 ` [9fans] I've got 4 student intern (undergraduates) here pac
2001-06-11 12:29   ` pac
2001-06-11 12:27     ` Axel Belinfante
2001-06-11 12:50       ` pac

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=E159SQT-0005qe-00@starfruit.iw3d.co.uk \
    --to=theo@ideaworks3d.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).