From: "qwx via 9fans" <9fans@9fans.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Curious about the state of Plan 9 / 9front in practice
Date: Fri, 16 May 2025 15:05:31 +0200 [thread overview]
Message-ID: <F8D059D27E9C9A222DDC0449573DBA9D@migadu.com> (raw)
In-Reply-To: <CAF=5iUUFRj5COfZ99Ctpgt4HP49hna8qWrHVoUK9QnQ0xNccjA@mail.gmail.com>
On Wed May 14 23:47:26 +0200 2025, lucas.francesco93@gmail.com wrote:
> Hi all, recently i've decided to make my compsci bachelor capstone
> project about a plan9 tool and I’m curious to know and it would be a
> bit relevant for me: what’s the current state of Plan 9/9front in
> actual practice? Are there any companies, consultancies, or platforms
> still using it in production or semi-production contexts—either
> internally or commercially? I understand it became a niche system, but
> I wonder if there are efforts where it sees real-world use beyond
> experimentation and the usual stuff we see around here, especially
> since it seems there was/is proprietary versions around. Also, are
> there specific roadblocks that you feel stand in the way of some niche
> use case that it's nearly viable? I would love to take those into
> consideration while writing my document.
>
> Thanks,
> Lucas
I don't know of any commercial products based on Plan 9 other than
those already cited, but it is being used in actual practice by a
number of people, some using real hardware, others through virtual
machines and drawterm, to do work beyond hobbyist projects. In my
case, my PhD project is about developing a tool for genome graph
visualization relevant to biologists and bioinformaticians and was
initially implemented and showcased on 9front before being ported to
Linux and others. I've heard of other researchers in Europe using it
right now in some capacity for their own projects, if only for
testing. In my branch of research, many existing popular tools
already work fine on Plan 9 through APE or NPE. The only thing that
makes Plan 9 impractical for applications is the memory allocator's
implementation (a lot of software just assumes it can allocate huge
buffers, eg. on a cluster) and the lack of a C++ compiler and various
dependencies. The leap from academia to industry is quite small
especially for non-copyleft projects. Both startups and the largest
bioinformatics firms use other opensource projects in their products,
often unmodified and as part of large data processing pipelines. More
broadly, you could draw comparisons between 9front and OpenBSD, which
is a relatively larger and much more well-known project, and you might
quickly realize that outside of ports, the differences in terms of
capabilities aren't particularly large. For my specific case, OpenBSD
is just as impractical because of performance and compatibility issues
across the board. Note that as far as I'm concerned, 9front is Plan 9
and vice-versa.
Cheers,
qwx
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td32c2e656057a991-Md2069afe7f0318d27e1c3146
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2025-05-16 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF=5iUUFRj5COfZ99Ctpgt4HP49hna8qWrHVoUK9QnQ0xNccjA@mail.gmail.com>
2025-05-14 23:58 ` [9fans] " hahahahacker2009
2025-05-15 3:51 ` Danny Wilkins via 9fans
2025-05-15 6:16 ` [9fans] " arnold
2025-05-16 13:05 ` qwx via 9fans [this message]
2025-05-16 15:59 ` tlaronde
2025-05-24 8:25 ` Ron Minnich
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=F8D059D27E9C9A222DDC0449573DBA9D@migadu.com \
--to=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).