9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Keith Gibbs <k@pixelheresy.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Software philosophy
Date: Wed, 18 Aug 2021 14:34:08 +0300	[thread overview]
Message-ID: <12DD420A-50B4-4270-A042-DFFF58F73BA6@pixelheresy.com> (raw)
In-Reply-To: <27f9d66f-4fe9-4c5f-b622-f11c7a231cfd@www.fastmail.com>

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

Come, come, Vester. Please don’t introduce false premises under the guise of calling them out. I never said that. 9front as the official Plan 9 would be pretty absurd.

I never said it was *the* development branch. It is *a* development branch. I could even imagine that it may in fact be the most popular and active for those wishing to develop new software on (with 9miller being very popular as well). 

If fact, I noted other projects... other Plan 9s as well in my initial and my response to Lucio. I was merely pointing out that Lucio in the past and in the OAuth thread keeps introducing the idea that the P9F should impose order and wall off everything but 9legacy [which he implies is the official one], even to the point of arguing in the past that 9front developers should port changes that are “good for the community” or some such to the “actual” Plan 9. 

Instea the charter for P9F's language was written to be inclusive. Why? Because historically this mailing list/community has been host to discussion for 9legacy, 9atom, 9front, p9p, etc. Even Inferno or Harvey come up semi-regularly. As such, it is not outside the general understanding of “Plan 9” as encompassing a wider berth. Although many of the P9F folk are contributors to 9legacy, I think they know that the community is broader and want all of it to be “Plan 9”.

So in the end, I apologise if it was unclear or confusing that I suggested to Lucio that 9front was to be "Plan 9 from Bell Labs Version 5”. It was a joke and everything I wrote following that should have made that very clear that I was arguing *specifically* for a plurality of Plan 9s rather than a single one [which Lucio was advocating for]. Lucio seems to hate 9front specifically for some reason, so the initial statement was intended as tongue in cheek.

Both 9legacy and 9front serve important niche functions within Plan 9 space, but neither *are* Plan 9. There is only one “official” Plan 9 and that was last updated January 2015. 9legacy positions itself as patch set on top of V4, but wants to maintain it in such a way that V4 will always function as V4. 9legacy maintains that it is not a fork. 9front says explicitly that it is a fork of V4 and a continuation based on it’s core principles. Both have fed into each other’s ecosystems. Hell, 9legacy’s site even says to run Plan 9 from Bell Labs rather than 9legacy if possible, which is kind of funny. And NIX is still active, last I heard, but currently has a closed community, not to mention Harvey and Jeanne.

So my main point was that we have a plurality and we *should* continue to have a plurality. Much like Lucio would find 9front as being blessed as “the official one true Plan 9” repugnant, so too would others re: 9legacy. A fair swathe of the Plan 9 enthusiast community want to build and evolve and a fair swathe want to preserve and maintain, with some incremental quality of life tweaks added in, and *both are totally valid*.

-pixelheresy

> On 18. Aug 2021, at 13.13, vic.thacker@fastmail.fm wrote:
> 
> Starting from a false premise does not help. 9front is not a development branch of Plan 9. Plan 9 is Plan 9. 9front is 9front. 9front is an open-source fork or derivation of Plan 9.  
> 
> Trying to make 9front the new and official Plan 9 does seem absurd. I'm not sure why there is a strong need for validation. 9front does not need official recognition. Let 9front be what it is. It can exist independent of the Plan 9 name. 
> 
> Sincerely,
> Vester 
> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T9ef6430f3025e731-M381a2c5d54ec68175eb453d4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2021-08-18 11:34 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 11:15 [9fans] OAuth2 in factotum Demetrius Iatrakis
2021-08-17  3:48 ` Lucio De Re
2021-08-17  7:47   ` Keith Gibbs
2021-08-18  3:55     ` Lucio De Re
2021-08-18  7:02       ` [9fans] Software philosophy Skip Tavakkolian
2021-08-18  7:19         ` hiro
2021-08-18 10:15           ` Lucio De Re
2021-08-18  9:46         ` Keith Gibbs
2021-08-18 10:13         ` vic.thacker
2021-08-18 11:34           ` Keith Gibbs [this message]
2021-08-18 11:47             ` Lucio De Re
2021-08-18 23:44             ` hiro
2021-08-19  4:34               ` Lucio De Re
2021-08-19 10:44                 ` Keith Gibbs
2021-08-19 18:53                 ` Git & Conventional Browsers (Was Re: [9fans] Software philosophy) unobe
2021-08-19 19:00                   ` ori
2021-08-18 11:34           ` [9fans] Software philosophy Lucio De Re
2021-08-18 11:28         ` Lucio De Re
2021-08-18 12:02           ` Keith Gibbs
2021-08-18 19:33             ` leimy2k via 9fans
2021-08-18 20:09               ` David du Colombier
2021-08-18 22:00                 ` Eli Cohen
2021-08-19  7:08                   ` Keith Gibbs
2021-08-19  7:59                     ` sirjofri
2021-08-19  9:27                       ` Lucio De Re
2021-08-19  9:45                         ` hiro
2021-08-19  9:51                         ` hiro
2021-08-19 10:10                           ` sirjofri
2021-08-19 10:38                         ` Keith Gibbs
2021-08-19 11:45                           ` hiro
2021-08-19 12:43                             ` Eli Cohen
2021-08-19 19:58                               ` Aram Hăvărneanu
2021-08-19 10:56                         ` kvik
2021-08-19 11:33                           ` sirjofri
2021-08-19 20:44                           ` ori
2021-08-19  9:29                       ` hiro
2021-08-19  9:44                         ` sirjofri
2021-08-19  9:19                     ` hiro
2021-08-22  2:46                   ` kokamoto
2021-08-22  3:16                     ` Eli Cohen
2021-08-22  7:07                       ` [9fans] Drawterm GPU (was: Software philosophy) sirjofri
2021-08-22 10:04                         ` Frank D. Engel, Jr.
2021-08-22 11:49                           ` sirjofri
2021-08-22 12:24                             ` Chris McGee
2021-08-18  9:18       ` [9fans] OAuth2 in factotum Keith Gibbs
2021-08-18 12:10         ` Ethan Gardener
2021-08-18 15:23         ` Stuart Morrow
2021-08-18 16:58           ` Stuart Morrow
2021-08-18 17:06             ` Sigrid Solveig Haflínudóttir
2021-08-17 15:25   ` ori
2021-08-18  3:59     ` Lucio De Re
2021-08-18  4:20       ` ori
2021-08-18  4:42         ` Eli Cohen
2021-08-18  5:06         ` Lucio De Re
2021-08-17  4:13 ` ori
2021-08-17  5:43   ` Lucio De Re
2021-08-19  3:52 ` Kurt H Maier
2021-08-19  5:38 ` ori
2021-08-22 20:16 ` ori
2021-08-22 20:32   ` Demetrius Iatrakis
2021-08-22 20:38     ` ori
2021-08-22 20:36   ` ori

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=12DD420A-50B4-4270-A042-DFFF58F73BA6@pixelheresy.com \
    --to=k@pixelheresy.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).