The link for this HN submission is unfortunately not a good portal wrt plan9. See [1] and [2].
1. https://groups.google.com/forum/#!topic/plan9port-dev/OqSvUD...
2. https://github.com/9fans/plan9port/issues/79
In A Tour of Acme (2012) [video]9fans
plan9port
C2016–2026
9fans / plan9port
plan9port
Plan 9 from User Space
22Distinct people
23Mentions
1Explicit recommenders
2KGitHub stars
What to know before exploring
What it is
Plan 9 from User Space
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Makefiles are underrated. The concept is so simple – it is basically a dependency graph with attached shell scripts – yet so powerful. Not just for building software, but also…
black_knight used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year23 dated mentions
Observed mentions: 2016-08-15 20:18:15 UTC to 2026-07-13 16:35:50 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
This is a port of many Plan 9 libraries and programs to Unix.
Installation
To install, run ./INSTALL. It builds mk and then uses mk to
run the rest of the installation.
For more details, see install(1), at install.txt in this directory
and at https://9fans.github.io/plan9port/man/man1/install.html.
Documentation
See https://9fans.github.io/plan9port/man/ for more documentation.
(Documentation is also in this tree, but you need to run
a successful install first. After that, "9 man 1 intro".)
Intro(1) contains a list of man pages that describe new features
or differences from Plan 9.
Helping out
If you'd like to help out, great!
If you port this code to other architectures, please share your changes
so others can benefit.
Git
You can use Git to keep your local copy up-to-date as we make
changes and fix bugs. See the git(1) man page here ("9 man git")
for details on using Git.
Status
Contact
Mailing list: https://groups.google.com/group/plan9port-dev
Issue tracker: https://github.com/9fans/plan9port/issues
Submitting changes: https://github.com/9fans/plan9port/pulls
Russ Cox rsc@swtch.com
Read the full README on GitHubWhat Hacker News says
4 sourcesFor the interested Plan 9 from User Space/plan9port is presently maintained at https://github.com/9fans/plan9port
More acme info at http://acme.cat-v.org
Acme has a cousin, sam: http://sam.cat-v.org
In A Tour of Acme (2012) [video]Concurrency is about how you organize a solution really more than anything. Whether those concurrent tasks execute in parallel or not is a different consideration. Many authors and experts conflate these terms.
You can write concurrent code with pthreads. It may happen to execute in parallel but it doesn't have to. In fact, I believe the early SunOS/Solaris pthreads had a 'green' scheduler where it could all be done in userspace (this is from my own memory nearly 20 years ago). This made them basically "stack switchers" which is what some lightweight coroutine libraries end up doing.
Having written heavily callback-driven code. Threading contexts manually, thinking about object lifetimes, I can say that coroutines have a much cleaner flow to them and can make it easier to write and later read and debug programs than crazy callbacks and co
Read the rest
ntexts.
Object lifetimes are one thing coroutines help with in a big way. I think it's why Rust is so attractive to so many.
Look at plan 9's libthread for example:
https://github.com/9fans/plan9port/tree/master/src/libthread
It allows one to take advantage of nonblocking sockets as a single "kernel execution entity" mechanism across many userspace threads.
This approach works pretty well. The Mongrel2 webserver clearly borrows this approach in their task library:
https://github.com/9fans/plan9port/blob/master/src/libthread...
https://github.com/mongrel2/mongrel2/blob/master/src/task/38...
I wonder how Acme[0][1], developed by Rob Pike for Plan 9 would compare. It feels fast and light, but I only ever use it for files lighter than a megabyte.
[0]: http://acme.cat-v.org/
[1]: https://github.com/9fans/plan9port
In Text Editor Performance Comparison