fluid-simulation-rust VS lumen

“Rust was originally designed as a systems programming language, similar to C/C++. However, it can also be used for front-end development. One way I have used Rust on the front-end is through WebAssembly. I previously worked on a project that involved building a fluid simulation in the browser. This involved implementing physics and mathematical equations. However, in order to create a visually coherent simulation, many iterations with different values needed to be performed. I initially implemented the simulation in JavaScript, and it worked well. However, I decided to try implementing it in Rust to see how it would compare in terms of performance. The difference was significant - the Rust version was able to perform more iterations in a fraction of the time it took the JavaScript version. You can find the fluid simulation here. Also, in the works, I am working on a library, app universe, that would help Rust developers manage frontend states. It is based on Chinedu's App world.”

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.