rustler_precompiled VS ractor

It's not a pain because of

https://github.com/philss/rustler_precompiled

The users of your library doesn't have to install anything. The library will seem like any Elixir library when they use it.

I created a elixir (wrapper) library to generate password hashes. Other Elixir libraries use a C NIF to generate password hashes. This libary uses a Rust NIF (using Rustler) and the Rust libraries the generate the different hashes. Additionally this library uses RustlerPrecompiled so you don't need to have a Rust compiler installed to use this library. It supports argon2, scrypt, brypt and pbkdf2.

We use the excellent Rustler Precompiled [1] library now so prebuilt binaries ship with the Elixir package. No Rust toolchain needed. :)

[1] https://github.com/philss/rustler_precompiled

This project also appears interesting, but it seems that its clustering features have yet to be tested in large scale distributed systems.

https://github.com/slawlor/ractor/discussions/131

If you look at my comment history, you'll see I'm well familiar with the BEAM.

I'm in full agreement with you, but I'm not sure you need full robust process supervision trees to mimic what the BEAM does in the context of LiveView on a single machine.

I do want to say, I 100000% times prefer Elixir, it's tooling, ecosystem, web frameworks, easy of scaling vertically and horizontally, etc over Go or any other lang that probably do something analogous to LiveView via what ever concurrency primitives that language/runtime champions; Go with it's Communicating sequential processes(CSP) and Rust with the Ractor lib (https://github.com/slawlor/ractor).

Also consider an actor framework like ractor. You can have actors listening to sockets, who will then message subscribed actor or actors with the data.

github