9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Tom Simons" <tom.simons@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] rio & acme & plan9
Date: Fri,  4 May 2007 13:08:35 -0700	[thread overview]
Message-ID: <2e4a50a0705041308l35428c44w2e16f8d26a72a22f@mail.gmail.com> (raw)

I have had trouble getting a handle on Plan9.  I got it working on an
old PC, but didn't understand if I had a file server, cpu server,
terminal, or all 3.  The screens looked great, but I never quite got
the hang of using it.  Can Rio/Acme run under Windows or Linux?  I'd
love to give it another shot. Must/should you have separate file/cpu
servers?

I also really would like to see an SF-bay meeting, if only to see
Plan9 in action. I've been using command-line interfaces since
teletypes & 026 keypunches, and I remain convinced that I could learn
another one.

>
> I've been trying to think of ways to evangelize rio and acme.  It's a
> tough sell - there is no "new user" subset.
> In particular, to be at all effective with rio (and especially acme)
> you need to be a capable command-line user and understand how to
> compose those primitives.  This means that no beginner will be able
> to pick up our beloved interface and get work done, even after giving
> them the 3-button low-down.  There just aren't any training wheels,
> and these days even expert users use the training wheels when in
> parts of the system they aren't familiar with.
>
> I think it's a losing battle.
>
> Paul
>


             reply	other threads:[~2007-05-04 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 20:08 Tom Simons [this message]
2007-05-04 20:13 ` erik quanstrom
2007-05-04 20:18 ` ron minnich
2007-05-05  2:17 ` Federico Benavento
2007-05-07  7:02   ` Wes
2007-05-07 17:57     ` Kim Shrier
2007-05-07 18:29       ` erik quanstrom
2007-05-07 19:00         ` Kim Shrier
2007-05-07 23:28           ` erik quanstrom

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=2e4a50a0705041308l35428c44w2e16f8d26a72a22f@mail.gmail.com \
    --to=tom.simons@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).