@lpil - What's the status of OTP interop? Seamless integration of Gleam GenServers (for instance) into an Elixir/Erlang supervisor tree would be important for usage on most projects (particularly if you want to do incremental adoption).

The last thing I read was that the plan was to re-implement a GenServer alike from scratch in Gleam rather than anything built over the top of the existing GenServer implementation. I can see why that might be necessary but that's slightly concerning given how battle tested the existing GenServer implementation is and all the edge cases it handles.

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 Erlang core (~200 lines). 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.