9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] architectures
Date: Thu, 12 Jul 2001 02:59:37 -0700	[thread overview]
Message-ID: <20010712025937.J78865@cassie.foobarbaz.net> (raw)
In-Reply-To: <20010712061553.C4EE7199E1@mail.cse.psu.edu>; from okamoto@granite.cias.osakafu-u.ac.jp on Thu, Jul 12, 2001 at 03:16:57PM +0900

On Thu, Jul 12, 2001 at 03:16:57PM +0900, okamoto@granite.cias.osakafu-u.ac.jp wrote:
> There are people and people who are using 'computers' now.  This may be
> false for many of such peoples, at least, some of them would be better to
> use such tools as "keitai" in Japan which has very limited buttons and even
> lacking keyboard.  It means that a kind of computer, road off from the main
> /real meaning of itself, will be neccessary to appear which does not look
> like 'computer' and very very limited usage for some particular purpose.
> Hmm, can we call it 'computer'?  :-)

I'm speculating on this, but I think it's where
we're going.

Computers are going to become more and more like
appliances; they will be in everything. Our greatest
hurdle is usability. Plan9 goes a long  way in the
realm of usability, but it's geared towards
programmers. You can't effectively make a system
that is usable for everyone; my mom couldn't use
Plan9. We need to consider that there are going to
be models of usability that cater to specific types
of usage/people. Not all users of computers are
programmers, nor should they be.

Don't get me wrong. As a geek, I love Plan9.

--
Christopher Nielsen - Metal-wielding pyro techie
cnielsen@pobox.com
"Any technology indistinguishable from magic is
insufficiently advanced." --unknown


  parent reply	other threads:[~2001-07-12  9:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  6:16 okamoto
2001-07-12  7:46 ` pac
2001-07-12  9:59 ` Christopher Nielsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-13  2:25 Rick Hohensee
2001-07-12 12:55 forsyth
2001-07-12 12:43 rob pike
2001-07-12 19:45 ` Boyd Roberts
2001-07-12 11:15 nemo
2001-07-12 20:28 ` Boyd Roberts
2001-07-13 14:53   ` Douglas A. Gwyn
2001-07-13 15:11     ` Boyd Roberts
2001-07-12 10:30 nemo
2001-07-12 10:18 ` Christopher Nielsen
2001-07-12  8:42 forsyth
2001-07-12 13:56 ` Laura Creighton
2001-07-12 16:13 ` Ozan Yigit
2001-07-12 16:33   ` Matt
2001-07-12 18:12     ` Scott Schwartz
2001-07-12 18:16       ` Martin Harriss
2001-07-12 18:43       ` Dan Cross
2001-07-13 14:52         ` Douglas A. Gwyn
2001-07-13 15:13           ` Boyd Roberts
2001-07-12  7:15 Sape Mullender
2001-07-12  5:22 anothy
2001-07-12  8:04 ` Matt
2001-07-12 10:12 ` Boyd Roberts
2001-07-12 13:01 ` Laura Creighton
2001-07-11 23:17 Jonathan Sergent
2001-07-11 17:59 David Gordon Hogan
2001-07-11 17:38 geoff
2001-07-11 18:29 ` Dan Cross
2001-07-11 16:27 jmk
2001-07-11 16:03 jmk
2001-07-11 15:17 nemo
2001-07-11 15:07 bwc
2001-07-11 16:53 ` Mike Haertel
2001-07-11 14:36 anothy
2001-07-11 14:59 ` Theo Honohan
2001-07-11 15:02   ` Matt
2001-07-11 16:52   ` Mike Haertel
2001-07-11 22:58 ` Boyd Roberts

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=20010712025937.J78865@cassie.foobarbaz.net \
    --to=cnielsen@pobox.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).