Fl4m3Ph03n1x

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?

Showing Posts 1 to 10

asummers

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.

jdumont

jdumont

To be brief… You say “done”, which makes Elixir sound like a project in and of itself, rather than a tool to complete other projects. Maybe it is? I don’t know. Many people have worked exceptionally hard to create a language, ecosystem of libraries/frameworks and a community that together is an outstanding tool.

Concerns over the direction of a language/framework/library, it’s adoption, it’s perception, etc are closely linked to the notion of languages as fashion items. These are matters for those seeking the language-du-jour, rather than a reliable tool with which they can work.

So, regardless of whether more work is done, or what exists will simply continute to exist (does that equate to stagnation?) — I and many others will continue to use Elixir for what it is: the best tool for the work I do.

wanton7

wanton7

It means that language is ready and it’s extendable enough and there will be no version 2.0. It will still get bug fixes and things like that. This means that you as developer don’t always have to learn new feature of the language and old code will be readable for years to come, it’s a good thing. This also means all those man hours can now be put into Erlang ecosystem & libraries (that Elixir is part of) instead, because you have this language stability promise.

12433412

12433412

In a hundred years, Elixir likely won’t exist. The process in which future applications are going to be generated shall challenge our imagination. Web dies. Keyboard/mouse/screen interaction dies. All goes its path. If you seek something eternal write code that changes the world forever. I would not worry too much about the language you choose to do so. :wink:

mythicalprogrammer

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.

jdumont

jdumont

That was entirely my point. Elixir in that context doens’t matter, only what you can do with it.

nolaxpat

nolaxpat

I was in the room for this talk and I don’t think he meant it like you’re interpreting it. He didn’t mean done as in finished, complete, no more work being done on it. He meant stable. In that talk, Bruce emphasized the 1 breaking change since 2014 I believe. That was a call to the enterprise, to those who are change averse out of necessity. Elixir is stable, he was saying, so it’s safe to come join us.

If you couple Bruce’s talk with Jose’s, you get the sense of a language moving very much in the direction of Python and the PSF. That’s a very good thing for Elixir in the long run. Far from being done, it basically means that it’s getting started for real now.

wanton7

wanton7

He is referring to this talk https://youtu.be/suOzNeMJXl0 at 54 minutes starts The next five years

eksperimental

eksperimental

I haven’t watched Bruce’s talk, but José explained it quite clearly in that ElixirConf talk

gregvaughn

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.

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews