From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Thu, 6 Sep 2018 14:37:51 +0100 [thread overview]
Message-ID: <1536241071.2844369.1498804520.321D1E43@webmail.messagingengine.com> (raw)
In-Reply-To: <20180906003258.9A428156E400@mail.bitblocks.com>
On Thu, Sep 6, 2018, at 1:32 AM, Bakul Shah wrote:
> On Wed, 05 Sep 2018 07:42:52 -0400 Chris McGee <newton688@gmail.com> wrote:
> > Could you get away with a much simpler, smaller hardware design and still
> > run Plan 9 in a reasonable way? Maybe one side of the software/hardware
> > divide has to take on more complexity to help simplify the other side?
>
> Look at what Prof. Nicklaus Wirth did for Oberon.
> https://www.inf.ethz.ch/personal/wirth/ProjectOberon/index.html
Oh I'd forgotten about Oberon! I started to look at it years ago, but assumed it was more complex than it actually is. It's hard to believe primary development only lasted 4 years. My point of contact with it was an OpenGL application with innovative culling of hidden objects. It was perfectly smooth, no latency; not bad for an operating system roughly in the same class as Inferno. One to put back on my to-do list.
>From the preface of P.O.System.pdf
> In spite of the small number of man-years spent on
> realizing the Oberon System, and in spite of its
> compactness letting its description fit a single book, it
> is not an academic toy, but rather a versatile
> workstation system that has found many satisfied
> and even enthusiastic users in academia and
> industry.
--
The lyf so short, the craft so long to lerne. -- Chaucer
next prev parent reply other threads:[~2018-09-06 13:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03 4:07 ` Lucio De Re
2018-09-03 12:40 ` Chris McGee
2018-09-03 17:58 ` Ethan Gardener
2018-09-04 10:51 ` Lucio De Re
2018-09-04 11:33 ` Ethan Gardener
2018-09-04 11:41 ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18 ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03 1:03 ` Charles Forsyth
2018-09-03 2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30 ` Tyga
2018-09-05 2:29 ` Chris McGee
2018-09-05 11:23 ` Dave MacFarlane
2018-09-05 11:42 ` Chris McGee
2018-09-05 13:35 ` Ethan Gardener
2018-09-05 15:38 ` Iruatã Souza
2018-09-05 23:59 ` Chris McGee
2018-09-06 0:32 ` Bakul Shah
2018-09-06 3:40 ` Lucio De Re
2018-09-06 11:41 ` Chris McGee
2018-09-06 13:37 ` Ethan Gardener [this message]
2018-09-06 17:48 ` Richard Miller
2018-09-06 19:08 ` Skip Tavakkolian
2018-09-06 21:21 ` Chris McGee
2018-09-07 8:32 ` Richard Miller
2018-09-05 3:25 ` Ori Bernstein
2018-09-05 8:19 ` Ethan Gardener
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=1536241071.2844369.1498804520.321D1E43@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).