9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] 9front on the Allwinner A64
Date: Tue, 29 Nov 2022 17:50:06 +0100 (GMT+01:00)	[thread overview]
Message-ID: <2aa0db47-52f7-4449-8e53-e5f43fade278@sirjofri.de> (raw)
In-Reply-To: <Y4YaXdwUJVEXk2cG@wopr>

29.11.2022 15:44:31 Kurt H Maier <khm@sciops.net>:
> Yes, this is what the hellaphone project was, but with inferno.  The
> Android pieces were basically hardware enablement and inferno tied into
> things like audioflinger.  There was no android UI left running.  You
> instead had a filesystem-based interface to the phone radio etc, with
> some basic touch-oriented UI served on top.  It was a similar approach
> to Mer's libhybris effort but with inferno doing plan-9-style things
> instead of lumping more linux on top.
> I suggest you look at what hellphone did before dismissing it entirely.
> I also suggest that before you start developing anything you come to
> some kind of definition of what Plan 9 "feels like."

I am very aware of what hellaphone did. Probably not that much into detail, but I really like their approach (besides having Android as a backend and that I generally don't really like the inferno UI stuff). Also I didn't really dismiss hellaphone entirely, my response was more towards the other mails in this thread.

I can start developing anything I like (as much as you can suggest anything you like), and surely, looking at what Plan 9 "feels like" is part of that development.

I think it's really hard (if not impossible) to find a definitive definition for that, especially considering "the user factor". But I believe it is necessary to develop something(TM) and give it to testers to see if it matches their expectations and extract the "Plan 9 feel" from user feedback to further improve.

Note that "develop" in this context doesn't mean a finak product, but also concepts and graphics that can lead to further discussion and improvement for the designs.


  reply	other threads:[~2022-11-29 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 19:45 sirjofri
2022-11-28  0:26 ` adventures in9
2022-11-28  7:56   ` sirjofri
2022-11-28 21:06     ` adventures in9
2022-11-28 21:20       ` unobe
2022-11-28 22:44       ` Kurt H Maier
2022-11-29  8:04         ` sirjofri
2022-11-29 14:42           ` Kurt H Maier
2022-11-29 16:50             ` sirjofri [this message]
2022-11-29 18:04               ` Tom Schwindl
2022-11-29 18:59                 ` adventures in9
2022-11-29 19:23                   ` Tom Schwindl
2022-11-30  2:38           ` Stuart Morrow
2022-11-30  6:34             ` adventures in9
2022-12-01 14:12               ` Stuart Morrow
2022-11-30  2:35       ` Stuart Morrow

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2aa0db47-52f7-4449-8e53-e5f43fade278@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --cc=9front@9front.org \


* 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).