As someone not that familiar with the subject, I found it easy to follow. Thanks.

Many async implementation are still based on thread pools. rust's tokio, node's libuv uses a thread pool for file I/O.

Before io_uring (which is disabled on most servers until it mature), there was no good way to do async I/O on file on Linux.

Sure async might be implemented by threadpools, but the threadpool itself is not what we usually refer to when we talk about async as a language feature.

e.g. Rust async may be backed by a threadpool, but it could also run single threaded.

My one man side project is Prisme Analytics: an high-perfomance, self-hosted and privacy-focused web analytics service.

I'm working on improving UX and simplifying deployment a lot. In the next release, a single docker run will be enough to get a working web analytics service with minimal resource usage.

[0]: https://www.prismeanalytics.com [1]: https://github.com/prismelabs/analytics

Cool lib! I took the same approach for my zero cost debugging assertion Go library

https://github.com/negrel/assert

Yes, there is HTTP Encrypted Content-Encoding (RFC 8188) which is used for Web Push that solves this exact problem.