9problems

The more specific the "fact" is to the target, the better IMO. - Bruce Schneier facts - https://www.schneierfacts.com/ - Doug McIlroy facts - https://github.com/mischief/9problems/blob/master/lib/dougfa...

> 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 channels it contains. Overall its a great library and I love working with thread(2). See this wonderful article on Go' history in code for comparisons between Go, Limbo, Plan 9 C and Alef: https://seh.dev/go-legacy/ [1] http://man.postnix.pw/9front/2/thread Might as well add a link to the source (that 9front repo is outdated, don't touch it): https://github.com/mischief/9problems/tree/master/sys/src/li...

Concurrency 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 (e.g. malloc'd memory or a segment(3)) so passing data around is just passing pointers to objects in shared memory. Further reading which demonstrates the library and how it influenced Go can be found here: https://seh.dev/go-legacy/

Old concept but Plan 9 c and thread(2) is simple yet really nice to work with. Also helps that there is no posix junk and plan 9 threads are light weight processes with shared memory. So libthread lets you spawn and manage processes or threads and groups them in rendezvous groups to guarantee sequential thread execution. That can eliminate the need for locks since no two threads in a rendez group will be running at the same time. Then use channels to read/write messages between procs. Way better pattern than async/await nonsense. http://man.postnix.pw/9front/2/thread example code (random 9 mirror I picked): https://github.com/mischief/9problems/blob/master/sys/src/li...