As already mentioned: it will only gain traction if/when less conservative developers and managers decide to use it. If everyone plays it safe, then no: it doe

As already mentioned: it will only gain traction if/when less conservative developers and managers decide to use it. If everyone plays it safe, then no: it doesn't stand a chance because Java, Go, JavaScript, Python (etc) already exist. But I would argue the decision to adopt Elixir isn't really as simple as a "this language" or "that language". The most essential decision, I would suggest, is about Erlang... not so much the language as much as the virtual machine and OTP. If the problem you want to solve is well solved by the BEAM/OTP, then you start to look at the languages you might use with the BEAM/OTP. I think BEAM/OTP is underappreciated for many use cases and that are worth exploring; this broadens if you consider BEAM/OTP augmented with more performant programs built with a language like Rust/Zig/C/C++. But if everyone plays the conservative game and doesn't see the risk/reward payoff with BEAM/OTP favorably... then it will be the same old boring players with only the ocassional influence from the sidelines.