From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: [9front] Re: [9front] Is 9front Generally Considered To Be The Successor To Plan9?
Date: Sun, 10 Mar 2024 19:16:22 -0400 [thread overview]
Message-ID: <29ECAD49-881F-4807-B5EF-136F7BD17AD6@stanleylieber.com> (raw)
In-Reply-To: <17101116980.dc049.73423@lsd.chicago.il.us>
On March 10, 2024 7:01:38 PM EDT, "Jay F. Shachter" <jay@m5.chicago.il.us> wrote:
>
>This is a 9front mailing list, to which Plan9 questions are routinely
>asked (e.g., "What is the Plan 9 equivalent of uname?").
>
>Is 9front widely considered to be the successor to Plan9, in the sense
>that, e.g., Fortran90 is the successor to Fortran77, such that answers
>descriptive of Fortran90 can be given to a question about "Fortran"?
>Similarly, can an answer descriptive of 9front be given to a question
>about Plan9? Or are there other incompatible operating systems that
>claim to be the successor to Plan9?
>
>(Parenthetically, and completely off-topic for this mailing list, the
>most recent standardized version of Fortran is Fortran2023, but does
>anyone in the real world actually use a version of Fortran that is
>less than 34 years old?)
>
> Jay F. Shachter
> 6424 North Whipple Street
> Chicago IL 60645-4111
> (1-773)7613784 landline
> (1-410)9964737 GoogleVoice
> jay@m5.chicago.il.us
> http://m5.chicago.il.us
>
> "Quidquid latine dictum sit, altum videtur"
>
>
there's no official anything, and nobody writing 9front code really cares about names. 9front forked from bell labs plan 9 in 2011. the concepts, and most of the features remain the same. it's probay fine to refer to any of the existing forks of bell labs plan 9 as plan 9, especially since the ones that diverged widely enough to raise objections have mostly ceased to be developed.
sl
next prev parent reply other threads:[~2024-03-10 23:18 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 ` Stanley Lieber [this message]
2024-03-10 23:26 ` Kurt H Maier
2024-03-11 0:11 ` ori
2024-03-11 9:57 ` hiro
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=29ECAD49-881F-4807-B5EF-136F7BD17AD6@stanleylieber.com \
--to=sl@stanleylieber.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).