protocol VS gleam

Here is the protocol I implemented in rust: https://github.com/moleculer-framework/protocol

Gleam GitHub Repository

Official Gleam Documentation

- https://without.boats/blog/revisiting-a-smaller-rust/

It's also niche, but https://gleam.run/ might be a candidate alternate language, depending on your use-case.

Not the other commenter, but my team has been using Elixir in production (soft real-time distributed systems) for several years to great success. The approachable syntax has been great for folks new to the language coming on board and sort of, not realising they’re “doing FP”.

Generally I’d say Elixir’s lack of “hard” static typing is more than made up for what you get from the BEAM VM, OTP, its concurrency model, supervisors etc.

That said if you’re interested in leveraging the platform whilst also programming with types I’d recommend checking out Gleam (https://gleam.run), which I believe uses an HM type system.

The BEAM runtime demonstrates the power of building concurrency and fault tolerance into the core runtime. While other languages can approximate these capabilities through frameworks, the elegance and robustness of having it built into the runtime remains compelling. I believe that’s why Gleam decided to use the BEAM when it was being built.

Gleam

Gleam as it says in their website is a friendly language for building type-safe systems that scale!.

One language that really gave me that feeling was Gleam, it managed to wrap everything I liked about languages such as JS, Rust and even Java into one brilliant type-safe package. Not for a long time before I met Gleam had I wanted to try creating so many different things just to get to the bottom of how this language ticked, as it were.

The two are pretty similar, but I would give F# the nod on this one example because it doesn't actually have to create a list of 200,000 elements.

[0]: https://gleam.run/