LucidMQ VS supervisionary

I'm using Cap'N Proto in a message broker application(LcuidMQ) I'm building for serialization. It has allowed me to created client applications rather quickly. There are some quirks can be difficult to wrap your head around, but once you understand it is really solid.

There are some difference between the language libraries and documentation can be lacking around those language specific solutions. I'm hoping to add blog articles and or contribute back to the example of these repositories to help future users in the future.

Check out my repo here for how I use it across Rust and Python, with Golang coming soon: https://github.com/lucidmq/lucidmq

I've been working on something that may fit your criteria. The API is kafka-like and it's whole goal is to provide an easy to use local-first stream datastore/data-engine.

It currently only has support for Rust and Python clients but working on expanding to node(JS) and C/C++ in the future.

https://github.com/lucidmq/lucidmq

If you're interested, check out the repo. Feedback is much appreciated to make this useful: https://github.com/bdkiran/lucidmq

Here's a proof-checker written in Rust for HOL, the same logic that Isabelle/HOL, HOL4, and HOL Light implements, up-to minor differences. However, the proof-checker has a very different design, compared to those systems, being written more like an operating system where proofs are constructed by issuing system calls (or, rather, calls into a Wasm host) and the kernel returning opaque handles to constructed objects to "user space".