Ryan Daum

This is I think the last task remaining for full MOO 1.8 full compatibility, and other than nailing down stability & bug fixes etc. it's the last thing blocking a...

Stateright is more immediately easier to integrate into a Rust automated testing workflow, and their examples show how to do that. However its examples and focus is primarily on distributed...

Added new test: https://github.com/rdaum/moor/blob/main/crates/db/tests/jepsen.rs

What needs to happen to get this change landed and released? We're running (@ my employer) with a local vendored fork (+ Rust bindings) and would prefer to be using...

Fix at https://github.com/eclipse/paho.mqtt.c/compare/master...rdaum:paho.mqtt.c:master I'd create a PR, but I'm not going to go register and sign the Eclipse contributors agreement just for this. Please apply it yourselves.

Pulling the discussion back to the original thread topic -- re: display/GUI layer, have you considered just starting with a curses/termio interface in order to get an MVP to test...

I don't have a lot of experience there but I think Ratatui is probably too far up the stack for something like Emacs, as it provides widgets, line editors etc....

One more thought on this general thread. I need to spend a chunk of time focusing on what you two have written here to absorb the threading model proposals, but...

Yeah I definitely think it would be a challenge do the Chrome-like process model if one is intending on GNU Emacs compatibility. You could do an Emacs, in the classical...

> Maybe consider writing a compatible layer(with low performance) in elisp? The emacs devel team also agreed on that the display engine is outdated and should be rewrited [mailing lists](https://lists.gnu.org/archive/html/emacs-devel/2021-12/msg02652.html)...