That is true. But some other models of concurrency (e.g. golang channels) _do admit_ static typing. This is a weakness of actor model adopted in BEAM.
Its a tradeoff -- do you go with untyped BEAM concurrency or typed concurrency like in golang.
Its a tradeoff -- do you go with untyped BEAM concurrency or typed concurrency like in golang.
In Go you have to write code to catch unwanted error and figure out what can go wrong.
So there are many things in Erlang where it soften this no type weakness.