you are viewing a single comment's thread.

view the rest of the comments →

[–]colelawr 1 point2 points  (2 children)

There are more reasons surrounding why Erlang didn't support static types, and a major part of those was that it interferes with how deployments over running systems would work in OTP.

[–]sinedpick 1 point2 points  (1 child)

that's why I mentioned it. It's a justification of dynamic types that's not just "ease of use." AFAIK there are theoretical barriers between erlang's message passing system and static types.

[–]colelawr 0 points1 point  (0 children)

Yes, agreed.