The distinction between language and runtime is right. I would disagree that Elixir improves issues of Erlang. I see it as plainly different, not a newer, bett

The distinction between language and runtime is right. I would disagree that Elixir improves issues of Erlang. I see it as plainly different, not a newer, better language on the Erlang VM. It does have the benefit of avoiding a few mistakes Erlang made (order of arguments in the standard library, for example), but for the vast majority of the time I spend developing in Erlang, that's a very minor part of it. The design objectives and decisions of the languages, the general tooling given (i.e. macros), and the approach the community takes to development has a much greater impact into how systems are shaped and built than the actual objective improvements they have done past Erlang mistakes that are the results of 25 years of existence, sealed in place through backwards compatibility promises. These are often not improvements, just a different way of doing it, and whether it's better or not will absolutely depend on the task at hand.