But the linked article, and much of the discussion here, is really about persuading more people to adopt Elixir. Essentially people are being asked to tie a period of their professional career to the fortunes of a technology.
Most of us code for money ... we have families to support etc. This is where a language becoming a "major player" becomes relevant, it's all about career investment. Part of the reason dev pays so well (for people who typically suck at salary negotiation) is the extreme mobility of programmers. However that does depend, to a degree, on the technologies you have experience with being widely used.
Niche technologies can leave you somewhat trapped in your current job ... and the people negotiating salaries and raises for employers will inevitably exploit this.
I liked it when Python had a smaller user base ... there was more of a "geek club" feel ... but there is no question that the remuneration for devs and the flexibility they enjoyed improved as adoption increased.
So ... there are financial risks to adopting Elixir ... but, if more people adopted Elixir this risk would fall away ... a classic dilemma. The problem is that everyone pushing the tech seems to be glossing over this dilemma, and the risk it presents to the people being pitched to. Now much of this can be attributed to classic geek enthusiasm over a superior technology (caught up in idealism ... not always pragmatic), but not all. For sure, the cheerleaders for every new technology will do this, but it is still somewhat disingenuous.
Right now I think this gap between tech idealism and career pragmatism may be the primary sticking point in increasing Elixir adoption ... but I feel it is wrong to try to bridge it but steering the next wave of adopters away from a realistic, informed assessment of the risks. Downplaying this is a step towards making fellow devs cannon-fodder in a mind-share battle.