From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme design (long)
Date: Mon, 7 Jun 2004 08:52:35 -0500 [thread overview]
Message-ID: <ee9e417a0406070652390d46ec@mail.gmail.com> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D066353@XMAIL.asuch.cas.cz>
You're not arguing about Acme vs. Oberon.
You're arguing about Plan 9 vs. Oberon.
As Rob said a few days ago, no one sat down and
said "let's build a system that's not like Unix", and
similarly no one set out to build a "non-Oberon".
Plan 9 and Oberon are both clean systems built
around simple (but different) models of how computing
resources should be presented. They each have
their advantages and disadvantages.
Once you accept that, it's easy to see that Acme is,
as Rob said in the paper, inspired by the Oberon
look and feel but adapted to the Plan 9 model instead
of the Oberon one:
Acme is a new program, a combined window system,
editor, and shell, that applies some of the ideas
distilled by Oberon. Where Oberon uses objects
and modules within a programming language (also
called Oberon), Acme uses files and commands
within an existing operating system (Plan 9).
There's not much point in answering any of the
specifics of your "debate" emails. You're arguing
about the relative merits of apples and oranges.
Good luck.
Russ
next prev parent reply other threads:[~2004-06-07 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 13:02 cej
2004-06-07 13:52 ` Russ Cox [this message]
2004-06-07 23:30 ` bs
2004-06-08 5:40 ` [9fans] wiki vdharani
2004-06-08 3:28 ` Russ Cox
2004-06-08 6:55 [9fans] acme design (long) cej
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=ee9e417a0406070652390d46ec@mail.gmail.com \
--to=russcox@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).