As someone who first came to Elixir from Erlang background, but also someone who has to work a lot with Python and hates every second of it... I'd need a compl

As someone who first came to Elixir from Erlang background, but also someone who has to work a lot with Python and hates every second of it... I'd need a completely different set of arguments. I don't like Ruby-like syntax. Not having something to separate expressions other than whitespace is a big turn-off for me. Something I also hate about Python. Something that a lot of forced Python programmers also see as a turn-off. Another, and perhaps superficial impression I got from Elixir is that it's Web-centric. I don't care about Web and have a strong distaste for everything that touches it. Python first appeared under the spotlight due to its Web framework, Zope, which kind of set the stage for that. Web had and still has a huge influence on how Python ecosystem developed, and that wasn't a good influence. I'd need an argument that says that Elixir is good outside of Web. I strongly believe that development speed is only in a very small part due to the language, and in a very big part due to how well you know the language. So, trying to convince me that the language is good because you could shave off a few minutes on a trivial task isn't going to convince me it's good. Working with large old programs is where productivity tools really matter because that where the bulk of my work goes to. But, really, I could never see the appeal of Elixir, when compared to Erlang. So, there's that. Also, I don't think it's worth it selling new technologies to Python programmers. Overwhelmingly, Python programmers are there either because it's popular and they like it, or because it's popular and they don't like it. Even in my first steps in Python world in early 2000's, I already knew there are better things than that. Quality was never a concern here, unfortunately.