stumpwm VS lumen

I don't have an answer for you, but just a note that v1.0.0 is 5 years old (almost to the day in fact): https://github.com/stumpwm/stumpwm/releases

Heads up, clx-truetype has an outstanding bug with XFT fonts causing a memory leak. Technically it's a forever inflating cache that can be periodically cleared but it's better to use a fork that fixes it. See StumpWM issue #861 on GitHub which links to more info.

You can do cool stuff in Common Lisp: differentiate, DSLs, CLOG, a 3D IDE, A Window Manager By the way: most of this is doable in other languages, too.

Welcome! Reading the manual and the code itself are the only tips I have. You can find some people's configs on GitHub and the like too by searching. Note that the manual on the website is very out of date, so use a local version after installing: https://github.com/stumpwm/stumpwm/issues/944

I think this all related to #669 which in turn is related to #532.

https://github.com/stumpwm/stumpwm/issues/843 Probably. Thanks

There are details on this also: https://github.com/GetFirefly/firefly#runtime

Generally it should be assumed that actors and their concurrency model is fully supported as that is a part of the core semantics for BEAM languages.

I think this project used to be called Lumen until pretty recently - https://github.com/GetFirefly/firefly

Probably not a practical solution for what you are building now, but it's worth pointing out Lumen, an Erlang VM implementation that compiles to WebAssembly, and could one day enable Elixir on the frontend.

Another vector could be some tooling that makes it easy to run Go programs compiled to Wasm run inside of Wasmtime environment hosted in Rust. If we run the go tooling in the same system, one could point this tool at a Go repo and be running that Go in a matter of milliseconds. A fun feature would be running channels across separate Wasm envs. Or maybe use Lumen.

Wish the Elixir WASM project -- Lumen -- were active. It seems like nothing much is happening on it.