goodboy

@salotz hehe fine by me. I actually mention `aka` and `orleans` in #18 funny enough. I guess linking the discussions is of use to some degree.

I started digging through the core of `locust` and was interested in how they do their multi-processing stuff to find out that they kinda, [don't do anything, heh](https://docs.locust.io/en/stable/running-locust-distributed.html#running-locust-distributed), despite having...

This is a [cool blog post](https://towardsdatascience.com/10x-faster-parallel-python-without-python-multiprocessing-e5017c93cce1) by the `ray` peeps that goes through comparisons with `multiprocessing`. Obviously they're cheating to some degree since the core of `ray` is C++. I...

This is somewhat implemented with our new `ContextCancelled` style signalling in the `Portal.open_context()` api. Work in https://github.com/goodboy/tractor/tree/zombie_lord_infinite also starts trying to apply the task-contexts stuff to regular rpc calls, and...

Woo found an example deploy script [in `msgspec`](https://github.com/jcrist/msgspec/blob/0.3.2/.github/workflows/docs.yml). This might play in with #157 which i've been meaning to get back to.

An interesting protocol I recently started reading about is [QUIC](https://en.wikipedia.org/wiki/QUIC) developed at google. It's branded as a *multiplexed-UDP*: a low latency TCP replacement and it's being slowly standardized and introduced...

@ryanhiebert it supposedly *is* sans-io as per: >Both the QUIC and the HTTP/3 APIs follow the "bring your own I/O" pattern, leaving actual I/O operations to the API user. This...

Some further QUIC resources. From the [wikipedia](https://en.wikipedia.org/wiki/QUIC): > QUIC uses UDP as its basis, which does not include loss recovery. Instead, each QUIC stream is separately flow controlled and lost...

Dropping this little project: https://github.com/lithdew/reliable

Linking this with https://github.com/python-trio/trio/pull/2047!