Fl4m3Ph03n1x
I have seen a podcast and now most recently a video (lonestar 2019) stating that Elixir is done:
What does it mean? Does it mean the core concepts are now completed for v1.0 ?
Does it mean the Elixir team will now go on a (well deserved) vacations and allow another team to take hold?
I have this idea that the community has to pick the direction where Elixir is going next, but everyone in a community wants different things. Some want types, some want more Nerves, others want more processes and others something more Haskell like.
I have trouble understanding what this all mean. Mostly, I fear this means Elixir will stagnate for the rest of year due to a lack of direction and purpose.
Can someone help me understand?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
That’s exactly right, the community is responsible for where the Elixir ecosystem is going. And if some prefer to make it more like Haskell and others to focus on Nerves. That’s totally fine.
What we refer as “done” (stable is a better word) is the Elixir language. We are not handing the codebase of the Elixir language to someone else. The goal is exactly to not change the language/core/foundation.
Also Liked
mythicalprogrammer
I saw in another post they said the language is mostly done and now they’re going to focus on adoption and spreading the words to companies and devs.
This basically is really good news since Erlang is quite a small language too. Coming from Scala having such a huge amount of syntax and keywords. Erlang and Elixir language are refreshing in being small and compact.
asummers
The idea is that Elixir has all the building blocks necessary to build libraries on top of it. Think of it as stable in the LTS sense or the Clojure sense rather than abandoned. To turn the question around, what features do you think are still missing that cannot be built on top of everything that already exists? Bugfixes and such will obviously still happen, and if something came up that could not be completed externally, they would add them to core. But at this point, I’m not sure what those things are.
gregvaughn
I saw both talks in person. I take it to mean “there are no breaking features (in the semantic versioning sense) in the plans for Elixir.” Feature enhancements will continue, but things are pretty stable, so build upon this foundation. I worry it is misconstrued.
Last Post!
mmport80
looking forward to Elixir 2 to 3 change!! : ))