I've been using Elixir for a little over a year now, running in production at modest scale (about 20 servers) for the last eight months. It's been a joy. I've

I've been using Elixir for a little over a year now, running in production at modest scale (about 20 servers) for the last eight months. It's been a joy. I've used a handful of languages and approaches to concurrency: from multi-process Perl-and-Fortran systems shouting at each other through named pipes, to Ruby + Resque, JRuby + threads, JS + callbacks/promises/streams, and Scala + Akka. Elixir has been easier than anything I've worked with before. I like the quote on this page by rtdsc: "I think more about passing state around and making it explicit." Elixir makes shared state just difficult enough to achieve that you don't do it by accident, and the fact that everything is immutable means that you can trust state once you have it. This kind of by-default hygiene is a godsend when writing highly reliable systems. I could go on and on about nice things in the language. I guess the best thing I can say is that it quickly becomes one of the least interesting parts of the stack. It just works. Wish I could use it everywhere!