I’m not the most knowledgeable but perhaps one of the major points would be making sure that elixir is totally usable from erlang somehow, I don’t know the amount of work that would entail or if it’s feasible and someone must already have thought of this, but something like a library in erlang that would contain the translation engine and make including an elixir dep/lib/file (in order of importance) in erlang seamless. It does seem like it might be a lot of work but if possible it would open up elixir to the remaining BEAM and kinda guarantee that it’s not only usable but of use for those writing in other BEAM langs and making investing in writing Elixir libs more rewarding?
Although I understand, it’s non-sensical to compare Elixir to Rails (? Ruby ?) in terms of adoption while excluding the context.
Rails came out in 2004, as did basecamp, when developing web-apps was not what it is today. This was when the web was booming and prior to 2008. The speed it afforded in development allowed people to start building things much faster. Shopify was started in 2006. Github launched in 2008. The fact it was much better for building fast MVP’s than anything that was there, and the usage by those high profile comps eventually just snowballed the adoption. This is also tied with things like heroku, which was launched in 2007, worked only with Ruby and allowed people to deploy in a single command a web app/site. If you looked at the landscape then, and saw these things all aiming towards making the life of a webdev easier, and focusing more on executing the “idea” than on technicalities it’s easy to see why you would choose a language that had so much momentum and was aligned with your goals as a web-dev and used as well in building those services/tools.
Django was 2005. And python kept on growing in usage in other areas.
Nodejs is 2009 but has the unholy advantage of js being the language for programming the client side. It’s just not comparable the advantage that gives in terms of adoption - the investment, the absolute treasure trove that entails having a registry that feeds packages directly to millions of computers and the promise of isometric web apps. The investment that went into the whole ecosystem probably dwarfs everything else in a wide range area. And we just tack on more into the babel (no pun intended) tower.
And this is ignoring things like Java, PHP, etc. Wordpress is from 2003.
Phoenix was 1.0 in 2015. Elixir launched in 2011. The, make a web app with a router, connect to the db, display, is solved (as in, it has solutions, independently of their shortcomings or advantages) by a long time now.
Erlang is older but its utility might be seen of being for different types of systems. It doesn’t help that it doesn’t follow either the C school nor the Lisp school, although most functional ideas are being introduced into “mainstream”, the programming models haven’t changed yet.
The problem with tech by the numbers/success cases is that for it to make sense you would need to include “well, this bank is using cobol and is valued at billions, sure this must be proof of its superiority”.