"So, we like Elixir and have seen some pretty big wins with it. The system that manages rate limits for both the Pinterest API and Ads API is built in Elixir. Its 50 percent response time is around 500 microseconds with a 90 percent response time of 800 microseconds. Yes, microseconds.
"We’ve also seen an improvement in code clarity. We’re converting our notifications system from Java to Elixir. The Java version used an Actor system and weighed in at around 10,000 lines of code. The new Elixir system has shrunk this to around 1000 lines. The Elixir based system is also faster and more consistent than the Java one and runs on half the number of servers."
These are pretty strong claims, I think.
You could do a poll of every developer and still have a different experience yourself. Most designers of new-ish languages know that accessibility is crucial to adoption, so they make it easier than you might think.
I personally have used lots of dynamic and static languages, and I will never go back to dynamic typing if I can help it. It's just a disaster when the code base gets really large and/or mediocre developers are working on it. For teams, the stricter the language is, the better. That's why I'm really enjoying TypeScript for now and looking forward to using Rust in the future (both for backend web development).
I'm about to embark on some experiments with isomorphic TypeScript apps, and that might be pretty revolutionary (and postpone my Rust experiments) because it allows me to use one pretty great language for the whole stack.
Another competitor is Go. People are afraid of functional languages because they think they are difficult to grasp and Go wins here because it is dead simple. Some say too simple, but any developer can get up to speed with it pretty quickly. It also has a better concurrency store than Node and some of the JVM languages. It's concurrency story is not as good as Erlang or Elixir, but in reality, many business and problems don't need that.
I think the market is going to pick something other than Elixir. I think it's going to be Go for a large set of problems (for many reasons) but for many problems people are going to stick with Java or JavaScript because they are ubiquitous.