goodboy

Another neat looking option is [data_pipe](https://github.com/random-python/data_pipe) which boasts some decent [benchmarks](https://github.com/random-python/data_pipe#benchmark). Found it through this [SO question](https://stackoverflow.com/questions/59008884/lmax-disruptor-in-python). Check the comments for claims about meeting requirements of an [LMAX style disruptor...

I've noticed many opinionated pronouncements about what does and does not constitute a true *actor model*: - Nathaniel's note on the [nursery naming thread](https://github.com/python-trio/trio/issues/504#issuecomment-486524940) seems rather strict about how structured...

Another blog with some interesting posts: http://www.dalnefre.com/wp/

Notes on how CSP vs. Actor systems mostly has to do with *asynchronous-ness* and naming: https://en.wikipedia.org/wiki/Communicating_sequential_processes#Comparison_with_the_actor_model

As a reminder to self, I would like to have a "formal stuff" spiel in the docs going over the comparison and supposed incompatibilities of `tractor` + SC. By almost...

Some further inside from an *existing systems* perspective: - the [supervisory policies and/or design in `akka`](https://doc.akka.io/docs/akka/current/typed/guide/actors-intro.html) which IMO [looks **exactly** like SC](https://doc.akka.io/docs/akka/current/typed/guide/actors-intro.html) especially when you [dig into what *behaviors* are...

rando link from @salotz on *The wide world of almost-actors: comparing the Pony to BEAM languages*: https://www.youtube.com/watch?v=_0m0_qtfzLs&t=1s

cute summary: https://gist.github.com/rbishop/9082539

@gc-ss > no guaranteed arrival order this is incompatible with TCP > cannot get lost and this is incompatible with the notion of UND in real systems > can arrive...

The *rant* task is codified in #210.