Despite its appeal to HN geeks I doubt if Elixir will ever achieve mainstream adoption. Searching Indeed.co.uk's API by title, there are only 5 Elixir jobs in London, compared with 445 Python and 171 Ruby. I also attended a Silicon Roundabout jobs fair recently and was disappointed to find Elixir wasn't even listed in the literature.
It's still early. I've bet on the wrong horse (stack) before, so take my comments with a grain of salt, but I know several companies that are currently adopting Elixir/Phoenix with the same level of excitement that I recall from the early days of Ruby/Rails. It may never be "Rails big", but there is definitely some momentum building.
Erlang has been around a lot longer, and is much more established. That could both support Elixir and work against it -- there are probably more Erlang jobs, but Elixir will benefit from the long-term demonstrated competence of the Erlang VM. I still wonder if it's just a fad. Personally I prefer Erlang, though I don't have really deep experience with either language.
When Rails arrived on the scene it was very different from everything else, but also there weren't 1000 new languages/ frameworks popping up all at once.
I'm not implying in anyway that Elixir is bad. I just think there are too many horses these days to know which to bet on. Elixir? Node? Go? Rust? Something else?
Rust is lovely for security-sensitive code - I'm writing a customer identity management system with Rust+Postgres+Redis.
Go is... acceptable... for "glue" code where PHP would've been used a decade ago and Perl before that - all the successes of it I've seen fall into that sort of pattern.
Elixir is great when you need to think about networked, stateful systems on the scale of a rack of machines - it provides many of the components to help you design systems at that scale.
So... as ever, they all do quite seriously different things. I don't think many people need to build the sorts of systems Elixir is good for - it'll always have its niche in large-scale communications systems, though. A good many webapps fall into the patterns that Go is good for - take user input, munge it, send it to some backend system. A fair bit of code that drives the foundations of what those webapps are built on will eventually be written in Rust.
Elixir is just alternative (Ruby-ish) syntax for Erlang, as much as people have hyped it up - Erlang code can call Elixir code and vice versa with essentially no abstraction cost. In fact, the most popular web framework for Elixir is heavily built on Erlang code.
Exactly. If Elixir didn't have to compete with Clojure, Rust, Go, Node, Scala and Kotlin it might have had a chance to become mainstream. Beyond the hype job stats are the ultimate indicator.
I was not talking about the job opportunities per se, just commented how in just about two years Elixir surpassed Erlang in its own niche. Just goes to say how an alien(prolog like) language syntax can really cripple the spread of state of the art technology. Thats why we never going to see Scala or Clojure be more popular than Java on JVM or Elm/Purescript/etc in browser. Because java and js are tolerable and have familiar Algol syntax... Not to mention that it can be said that most of the alternatives I have listed have unusual syntax.
Just saying but most companies that search elixir dev do not go in this website. They immediately go for the community. Faster, easier and you get more consistent results.
Difference between hiring "someone that knows it" and "a good dev interested by it"