One problem with having Erlang/Elixir statically typed is that it would make the dynamic code loading very difficult, if not impossible, to implement.
We could have “dynamic loading code” of of box in era of containers (docker swarm, kubernetes, reload code == update version of image ), but yes depends of situation and need like embedded devices it is useful feature to reload code .
1 Like
NeverMind. 
2 Likes
Indeed, that is why that I keep saying that the statically typed parts should be groups of modules, and all communication otherwise is via black-boxing messages (like the dynamic type I mentioned above). ^.^
If you hot-code swap well you are swapping a release in full anyway, and the code update function can update the data models too (it would be cool to build versioning into the types especially!).
1 Like
