moor VS otp

I think Haskell or OCaml would do a better job on the ADTs for a parse tree. When doing this, I found Rust's enums... anemic... and got very annoyed by the awkwardness of having to Box recursive types. I was reaching for the ability to continue to be able to pattern match on nodes while attaching common attributes (line numbers, etc.) and ended up having to bury everything 1 level deep in a struct which ended up feeling awkward.

That and Rust's iterators are terrible at introducing ownership agony.

In any case, I've ... done it (https://github.com/rdaum/moor/blob/main/crates/compiler/src/...) but can't say I liked it.

I do really like "pest" as a parser generator though.

See: https://github.com/rdaum/moor

I've been working on a rewrite of the server into Rust, for kicks: https://github.com/rdaum/moor

Unfortunately still lots of work there to be done, and I have no time.

Modern type system over BEAM sounds great but unfortunately OTP is still not 100% supported https://github.com/gleam-lang/otp?tab=readme-ov-file#limitat...

They seem to have rewritten/wrapped OTP, but it's not production ready. https://github.com/gleam-lang/otp

YMMV, but a BEAM language without OTP severely limits its appeal and usability.

Looks like it is an external library[^1]. Readme states it is experimental and lists some limitations.

[^1]: https://github.com/gleam-lang/otp

We have a fully type safe and OTP compatible implementation of actors and supervisors here https://github.com/gleam-lang/otp

No primitives as it's not possible to have them when compiling to JavaScript, but we do have them as types and functions in the OTP library https://github.com/gleam-lang/otp

On the advice of u/WrongJudgment6 I'm reading the Gleam OTP tests. But I can't compile, and hence can't test, the code. (I'd like to do that so I can tweak the tests to do my own experiments.) Whenever I try I get an error like this:

And docs at https://hexdocs.pm/gleam_otp/

We have a fully type safe and Erlang compatible OTP library! It is used in production today.

https://github.com/gleam-lang/otp

It is not a wrapper around gen_server etc, but instead it is a full implementation from the ground up using a very small core. This was done because:

a) Erlang OTP cannot be typed, we need different abstractions are designed with types in mind

b) We want to be confident that our abstractions are powerful enough to build something like OTP, rather than cheating by relying on type casts.

I'm very happy with how Gleam OTP is going, but it is not the focus now that an initial version is out. Tooling and documentation is more important at the moment.