Top all-time · #7461
seh.dev
Personal blog · seh.devprogramminghistory
seh.dev is a personal blog at seh.dev about programming and history. Since 2020, 10 different Hacker News readers have linked it 19 times, most often “Go's History in Code (2020)”. The last post was in 2022, but the archive is still widely read.
some kind of blog
Most-linked posts?
- Go's History in Code (2020)4 people · 12 mentions · first linked 2020-06-23
- Polymorphism in Limbo and Go 22 people · 2 mentions · first linked 2020-10-08
- Program development in Limbo (the native lang of Inferno, Unix 3.0)2 people · 2 mentions · first linked 2020-11-09
What Hacker News says?
See also: https://man.9front.org/2/thread The history of this concurrency model is here: https://seh.dev/go-legacy/
Comment linking /go-legacy/
on “How I turned Zig into my favorite language to write network programs in”Submitted Writing UTF-8 Programs in Plan 9 as a story · 51 points
HN discussion> The BEAM is fascinating for many reasons, including being register-based. > I really just wish the BEAM was portable in the way the JVM is. Inferno is both register based and highly portable using the same tool chain as Plan 9 which runs seamlessly across multiple architectures. This eventually evolved into the Go tooling as Rob Pike came up with the Plan 9 design and worked on it with Ken Thompson. https://seh.de…
Comment linking /go-legacy/
on “Writing your own BEAM”Submitted Program development in Limbo (the native lang of Inferno, Unix 3.0) as a story · 4 points
HN discussionInferno was a commercial attempt at competing with Sun's Java. The plan 9 folks had to shift gears so they took Plan 9 and built a smaller portable version of it in about a year. Both the Plan 9 kernel and Inferno kernel share a lot of code and build system so moving code between them is pretty simple. The real interesting magic behind Plan 9 is 9P and its VFS design so that leaves Inferno with one thing going for i…
Comment linking /go-legacy/
on “The Unix-Haters Handbook (1994) [pdf]”Submitted Go's History in Code (2020) as a story · 3 points
HN discussionPrior art: http://man.postnix.pw/plan_9/2/thread (Plan 9's thread(2). Personal note: I absolutely LOVE working with this library) https://swtch.com/libtask/ (Rus Cox's portable library (Someone on the 9fans mailing list ported it to a micro-controller)) See Also: https://seh.dev/go-legacy/ (A nice code tour of the historical CSP lineage of Go) https://swtch.com/~rsc/thread/ (Bell Labs and CSP Threads)
Comment linking /go-legacy/
on “libmill - Go-style concurrency in C”Submitted Go Patterns – Fanning as a story · 3 points
HN discussionConcurrency is easy if the library is well thought out and clean. So I much prefer the Plan 9 approach using the CSP thread(2) library: http://man.postnix.pw/9front/2/thread , Example program: https://github.com/mischief/9problems/blob/master/sys/src/li... Wonderful easy to use library which is built on top of rfork and uses channels and alternates to synchronize the procs. Heap memory can be shared across processes…
Comment linking /go-legacy/
on “Posix Threads Programming”Submitted Program Development in Limbo for Inferno OS as a story · 3 points
HN discussionIf you're looking for C-like languages to study look up the plan 9 Alef language. It was a concurrent C-like that was designed to replace C until they realized its better off as a C library which is what plan 9's thread(2) is. It's mostly extinct but survives: http://doc.cat-v.org/plan_9/2nd_edition/papers/alef/ https://seh.dev/go-legacy/
Comment linking /go-legacy/
on “Show HN: A work-in-progress C compiler from scratch”Submitted Polymorphism in Limbo and Go 2 as a story · 3 points
HN discussionInferno was Lucents answer to Sun's Java and was intended as a commercial product. They stopped all Plan 9 development for a year to work on it. The big difference and attraction to me are the pure VM user space and the dual build path where you can build it for bare metal or hosted on a number of operating systems (Plan 9, Windows, BSD, Unix, Linux, web browser, etc.) That way you can run Inferno applications just…
Comment linking /go-legacy/
on “F/OSS Comics: 8. The Origins of Unix and the C Language”Submitted Playing with Oberon in 2019 as a story · 2 points
HN discussionhttps://swtch.com/~rsc/thread/ https://spf13.com/presentation/on-the-shoulders-of-giants/ https://seh.dev/go-legacy/
Comment linking /go-legacy/
on “Inferno: A small operating system for building crossplatform distributed systems”Submitted Polymorphism in Limbo and Go 2 as a story · 2 points
HN discussion> The real essence of Go channels is their ability to participate in the built-in select keyword. Select is similar to a function in plan 9's threading library[1] (which is part of the Go lineage) called alt(). To use it you stick it in a switch like so: switch(alt(alts)) {}. Select {} is syntactic sugar for some alt like functionality. Of course the programmer is responsible for setting up the alt structure and the…
Comment linking /go-legacy/
on “Go-like channels in 10 lines of JavaScript”Submitted Go's History in Code as a story · 2 points
HN discussionSubmitted Go's History in Code as a story · 2 points
HN discussion
