Elixir 1.20 Released with Gradual Typing
Executive Summary:
- Elixir 1.20 introduces gradual typing for improved code safety and performance.
- Developers can expect faster compilation times for large applications.
- The Elixir ecosystem continues to evolve with a focus on usability and performance.
The Internet’s Verdict: 70% Hyped, 30% Skeptical
Community Reaction
Developers are discussing the implications of gradual typing on program performance.
I’ve seen various posts about Elixir’s gradual type system pop up on HN, but haven’t been following too closely. Does anyone know whether this particular gradual type system can change the asymptotics of programs vs untyped code? As far as I’m aware, most gradual type systems (e.g. Racket) can make programs run asymptotically slower, although there are some exceptions.
Performance Improvements
Some developers are already seeing benefits from the update.
This is great, and it looks like 1.20 is compiling our large umbrella app quite a bit faster.
However, others are still hesitant due to the learning curve and ecosystem challenges.
Oh shit here I go (and learn Elixir for a whole year (again)) again. I love everything about Elixir, but Elixir constantly makes me doubt myself like no other language. My brain isn’t made for functional stuff, but this makes me want to try again.
Found elixir intriguing and so Phoenix. Two reasons I put it aside again are: You need Beam and the Elixir. I find that really weird, because I’m used to just the language like in Python, Java, C, Rust. Not something underneath it, too. There is no debugger. The way to debug Elixir is to print stuff to the console, like 40 years ago. No thanks.
Focus Keyword: Elixir 1.20
