Checking out if I can use https://gleam.run for most of my code and just have the necessary parts like Phoenix and Ecto in Elixir.

With regards to alternative BEAM languages, I’m currently learning Purerl, which is Purescript with Erlang as the backend. The interop story is very good: running PS code from Elixir is very easy, and FFI in Purescript seems to also be frictionless. They also have OTP, Gun, etc bindings. However, I can see why it didn’t get more traction: I’ve been studying it for a couple weeks, I’ve writtern monad transformers but I still don’t know how to make a simple GET request . But, it’s fun and powerful, so I’m looking forward to learn it and eventually use it with my Elixir code.

I always try to use Dialyzer and typespecs as much as possible. Even for project where I don’t use Dialyzer, typespecs are used.

At work, Dialyzer warning are tracked by our CI-tool. Builds don’t fail when introducing Dialyzer warnings, but there is a strict agreement om fixing those warnings as quick as possible.

I have tried several of the other tools, but they simply don’t work on our code base - they usually crash in one way or another.
Would love some faster and more accurate type analyser tools, but for now Dialyzer works and does indeed find potential issues.

I will! Currently I’m writing a little code generation thing so that I can read Ecto schema structs in a type safe way in Gleam (I’m calling it Neglecto). But I’ll post a separate thread about it if it goes somewhere.

We use Dialyzer and CI fails if there are any warnings. Also, we recently enabled the unmatched_returns flag, which I can recommend.

Regarding other tools, I thought about trying TypeCheck and enabling it in tests. Given good coverage, I’d expect it to be quite accurate.