9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] UI design | enhancements.
Date: Mon, 15 Apr 2019 11:10:00 -0400	[thread overview]
Message-ID: <CAOk9ws351wE=DuLMfpFdJVD8XUMUXxvLU4y4dZ9oOcD3ED0vpg@mail.gmail.com> (raw)
In-Reply-To: <d788974f-a919-3ca6-06d1-7004daef02e1@wisecorp.co.uk>

[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]

Hi Darren,

Your goal seem to be to make the system less daunting for new users. I
think there are a number of ways to accomplish this.

Dressing up the UI and/or making it more like popular used interfaces might
be one way to make new users feel more comfortable. One concern with doing
this is that it allows them to come with other assumptions that may
confusions about how the underlying system works. This effort could also
increase complexity and size of the core system. Simplicity, size and
consistency are aspects of Plan 9 that I really value. Otherwise, I might
as well just use BSD or even Linux.

In my experience one of the biggest hurdles to getting curious new users to
give Plan 9 a try is just getting access to a namespace so that they can
give it a try and learn. I think that the quickest path at the moment is to
install it onto a VM like qemu (or yuck, virtualbox) since you can bypass
the whole hardware selection and compatibility pain points. I put some
YouTube videos up showing people step-by-step with a decent number of views
and comments, so I think this helped some people just to get their hands on
it. There are more ideas that I'm playing with to help people get started,
such as building a website where you can get a drawterm in your web browser
and give it a try.

Once a new user has access to the system there could be some exercises and
tutorials to engage them. There could be a variety of these depending on
the background, whether programmer, Linux user, librarian, whatever. The
key in my opinion is to not hide the core system with layer after layer of
"pretty" GUI's, but instead reveal it gradually with decent explanations. I
think that the core of Plan 9 is much easier to explain than other systems
because of its smaller size, relatively consistent interfaces and
versatility. Once you grasp one area it is much easier to begin grasping
more of it using the skills you already have. I can't say the same thing
about Linux or any other system that I have used. Like any tool, there is
some required learning and practice. Good tools amplify your learning as
you practice with it.

Once someone understands how Plan 9 works then I think they will have many
of the tools that they need to build their own networks with it. I
recommend digging into man pages and /sys/doc at this stage. There's a
wealth of well written guides in there, although some could be made a bit
more current. A guide on how to build a home network using raspberry pi
terminals and a CPU/file server from easy to acquire, but well designed,
modern hardware would be a welcome addition.

The system is far from perfect as others will tell you but there's advances
and fixes happening steadily. I'm just not sure if focusing on the initial
user experience through UI look and feel is adding much. I think a more
general discussion of GUI capabilities, such as video and 3D graphics
capabilities, would be great, but more in the context of what kinds of
tasks people want to accomplish. The trick is to fit those improvements
into the rest of the system and not just jamming them in.

Cheers,
Chris

[-- Attachment #2: Type: text/html, Size: 3399 bytes --]

  parent reply	other threads:[~2019-04-15 15:10 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  4:41 [9fans] Git/fs: Possibly Usable ori
2019-04-02  6:10 ` Skip Tavakkolian
2019-04-02 13:32 ` Dave MacFarlane
2019-04-02 14:37 ` Kyohei Kadota
2019-04-03 10:38 ` Giacomo
2019-04-03 18:29 ` Skip Tavakkolian
2019-04-03 20:14   ` David du Colombier
2019-04-03 20:23   ` Ori Bernstein
2019-04-04  0:00     ` Skip Tavakkolian
2019-04-04  0:34       ` Kurt H Maier
2019-04-04  1:22     ` Ori Bernstein
2019-04-14  9:58       ` [9fans] UI design | enhancements Darren Wise
2019-04-14 11:30         ` Ethan Gardener
2019-04-14 14:19         ` hiro
2019-04-15  5:07         ` Lucio De Re
2019-04-15  6:12           ` Bakul Shah
2019-04-15  6:25             ` Devine Lu Linvega
2019-04-15  6:41               ` Michael Misch
2019-04-15  7:24                 ` Bakul Shah
2019-04-15 11:20                   ` hiro
2019-04-15 14:27                   ` Kurt H Maier
2019-04-15 19:59                 ` Ethan Gardener
2019-04-15 20:04                   ` Michael Misch
2019-04-15 15:10         ` Chris McGee [this message]
2019-04-15 15:44           ` Darren Wise
2019-04-15 18:11         ` ab
2019-07-08 19:54 ` [9fans] Git/fs: Possibly Usable Ori Bernstein
2019-07-12 18:27   ` Patrick Marchand
2019-07-12 20:21     ` Steve Simon
2019-07-21 21:06       ` clueelf
2019-07-25 21:59         ` Ori Bernstein
2019-08-05 18:43           ` Skip Tavakkolian
2019-08-05 21:17             ` erik quanstrom
2019-08-05 21:22               ` erik quanstrom
2019-08-09  5:56             ` Ori Bernstein
2019-04-15 15:47 [9fans] UI design | enhancements ori
2019-04-15 20:59 Marshall Conover
2019-04-15 21:10 ` Ori Bernstein
2019-04-16 12:54   ` Marshall Conover
2019-04-17  3:57     ` Lucio De Re
2019-04-17  4:02       ` Michael Misch
2019-04-17  4:25         ` Lucio De Re
2019-04-16  8:17 ` Mart Zirnask
2019-04-15 21:51 sl
2019-04-16  3:54 ` Lucio De Re
2019-04-16 10:21   ` 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='CAOk9ws351wE=DuLMfpFdJVD8XUMUXxvLU4y4dZ9oOcD3ED0vpg@mail.gmail.com' \
    --to=newton688@gmail.com \
    --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).