9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] emacs vs plan9
Date: Fri,  9 Apr 2004 23:32:27 -0700	[thread overview]
Message-ID: <A04405DC.2575C7D3@mail.gmail.com> (raw)
In-Reply-To: <200404100611.i3A6BqkH081228@adat.davidashen.net>

saying 'everything is an edit buffer' doesn't get you very far.
you still need to talk about naming, authentication, security,
remote access, and so on.  you do get a user interface, though,
and that is clearly a powerful starting point.

saying 'everything is a file' brings along with it everything to
do with files that we're already familiar with: naming, permissions,
security, and so on.  a really telling detail is that network file systems
are well understood, so if we make everything a file we immediately
have remote access to everything.  we don't have a user interface
to something, at least the way emacs has (editing etc.) but we do
have shell scripts and other ways to build things from basics.

'better' is a bad term when comparing system design.  the goals
of systems differ.  but i think that 'file' brings more powerful and
systems-capable ideas to the table than does 'edit buffer'.

-rob


  reply	other threads:[~2004-04-10  6:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  6:11 David Tolpin
2004-04-10  6:32 ` Rob Pike [this message]
2004-04-10  7:41   ` David Tolpin
2004-04-12  1:54     ` Kenji Okamoto
2004-04-10 16:28 ` ron minnich
2004-04-10 16:53   ` boyd, rounin
2004-04-10 16:55   ` Russ Cox
2004-04-12  2:14     ` ron minnich
2004-04-10 18:19 Keith Nash
2004-04-12  2:16 ` 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=A04405DC.2575C7D3@mail.gmail.com \
    --to=robpike@gmail.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).