3 ms·
I understand why dynamic typing might be needed for code reloading and multiple nodes. However for an overwhelming number of uses a single erlang node is suffic
by sidkshatriya 5y ago
I understand why dynamic typing might be needed for code reloading and multiple nodes. However for an overwhelming number of uses a single erlang node is sufficient and code reloading itself comes with additional complexity that it is only useful for rare applications. On the other hand hand static types give you cheap and easy freedom from a large class of bugs. Erlang spends a lot of time bringing reliability through sophisticated patterns such a supervision trees etc etc but then totally fails by having dynamic typing. I love Elixir/Erlang but I would say that here (provocatively perhaps) the platform is penny wise and pound foolish: It spends a lot of time on sophisticated strategies while omitting the most elementary one: static types. I like the platform but like every platform it does have weaknesses. To me, personally, missing static types is a weakness.
- linkdd 5y agoYou may want to take a look at https://gleam.run/ https://gleam.run/
- brightball 5y agoGleam might be what you need then. The combination of strong types, dialyzer, guard clauses and pattern matching has been more than enough in my experience. Fully static typing doesn’t bring its benefits without costs.