9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Is 9front Generally Considered To Be The Successor To Plan9?
Date: Mon, 11 Mar 2024 10:57:14 +0100	[thread overview]
Message-ID: <CAFSF3XMsREYFGyqD-1wTz-jMqCEJYxSLGChuzVreBMYNj=1eHQ@mail.gmail.com> (raw)
In-Reply-To: <17101116980.dc049.73423@lsd.chicago.il.us>

> Is 9front widely considered to be the successor to Plan9, in the sense

no.
the problem is that plan9 is not widely considered in the first place.
of the few people that heard about plan9, i suspect fewer have heard
about 9front. this is a testament to the stability of this ecosystem.
C code is portable, between architectures, and also between plan9
forks.

      parent reply	other threads:[~2024-03-11  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 23:01 Jay F. Shachter
2024-03-10 23:16 ` [9front] " Stanley Lieber
2024-03-10 23:26 ` Kurt H Maier
2024-03-11  0:11 ` ori
2024-03-11  9:57 ` hiro [this message]

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='CAFSF3XMsREYFGyqD-1wTz-jMqCEJYxSLGChuzVreBMYNj=1eHQ@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \
    /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).