Elixir v1.20: Now a Gradually Typed Language
- Elixir v1.20 introduces gradual typing to improve code reliability.
- The new typing system does not require changes to the language syntax.
- Developers can benefit from improved code maintainability without sacrificing flexibility.
The Buzz Score
The Internet’s Verdict: 70% Hyped, 30% Skeptical
Forum Voices
Developers are discussing the implications of Elixir’s new gradual typing system. Some believe it’s a step in the right direction, while others are skeptical.
Honest question, in the era of vibe and AI assisted coding is there any advantages of using untyped programming languages, apart from the fact that non-typed languages has more training data for the LLM? This probably controversial, but personally I consider untyped languages as technical debts that need to be fixed sooner or later, and the OP article is partly addressing this very issue.
Others have shared their experiences with Elixir and its lack of static types.
I wanted to use functional programming in actual projects and Elixir’s lack of static types almost stopped me from picking it up initially. I tried it out and, although I do miss static types sometimes, immutability and not having to deal with inheritance and other OO abstractions has made the trade-off worth it for me.
Conclusion
Elixir’s gradual typing system is a significant update that can improve code reliability without sacrificing flexibility. While some developers are excited about the change, others are more skeptical.
Focus Keyword: Elixir v1.20
