eventually-rs VS thalo

While I like now that there is a single trait involved (which also makes it easier to write super-types), I don't like the requirement for those associated type names like type GetError and type SaveError. I also don't particularly like the idea of hiding everything behind a single Error type, as it kinda defeats the purpose of having such a nice type system like the one Rust has.

But you can read it in the Rust version README! :D

Thalo is a new Rust library that provides a runtime for WASM-based event sourcing. With Thalo, developers can compile their aggregates and components into WASM modules and use them in the runtime to handle commands and persist events to an event store. The library is built on top of Wasmtime and Message DB, and uses the ESDL schema language to define aggregates. While Thalo is not yet ready for real-world use, it has the potential to make event sourcing more accessible to a wider range of languages that compile to WASM, allowing for a language-agnostic runtime. Give it a try and let us know what you think! https://github.com/thalo-rs/thalo

Over the past couple of months I've rewritten a project of mine from scratch called Thalo. https://github.com/thalo-rs/thalo

Interesting! Thanks for sharing. I can see how macros can be heavy, but yours was pretty light IMO. Comparing with the current example, the current one has basically the same code, plus the edsl code that looks like a header (if Rust ever had C's .h or OCaml's .mli files). Which isn't necessarily a bad thing though.