Where are you located?
Are you a freelancer?
gausby
Zesky665
lpil
Creator of Gleam
If I were to leave Elixir/Erlang it would likely be because of the dynamic type system. Over the last few years my development style has changed and I’ve found myself more comfortable and productive with static type systems.
I’ve not yet left Elixir/Erlang because the productivity boot I get from Elixir/Erlang and the BEAM is greater than that I get with static types. Hopefully one day I’ll be able to have both types and the BEAM 
a monoculture around libraries and frameworks (phoenix, ecto, mix, cowboy)
I hear that. It would be great if the alternatives to Phoenix, Ecto, and Cowboy had more momentum.
I think rebar3 is an good alternative to mix, so I’m happy there, ignoring the problem of Elixir libraries (IMO) miss-use of Mix.Config.
11
dimitarvp
Why though? What exactly is to be gained?
Apart from Raxx which claims to address the streaming sockets paradigm better than Plug – something I cannot confirm or deny because I haven’t used websockets yet – I have never seen libraries that are able to disrupt Phoenix, Ecto and Absinthe in a compelling manner.
There are many others that don’t aim at disrupting them. And most of them are doing very well.
2
lpil
Creator of Gleam
Not getting into the details of any specific libraries, I think ecosystems benefit when there are multiple teams collaborating and competing in the same problem space.
6
superherointj
On your spreadsheet/poll mark my vote only to: “Improve correctness.”
(Static type system. Catching errors before execution not after.)
Thanks for asking! =]
3
nsweeting
I dont see myself moving away from Elixir anytime soon. Over the last couple years I usually start attempts at learning a new language, and have yet to find one that can match the ergonomics that Elixir can provide.
I’ve been fortunate to have pushed Elixir fairly early at my company. And to have been in a position that my voice can be heard. Started with microservices, and have since moved on to going through the full development cycle of 2 fairly large applications. We were mainly a Ruby shop before - and I dont think we could have really achieved the same results as what we currently have in place. Certainly not in terms of server costs. We have another largish Ruby app that is similar in scope to one of the Elixir apps - and it easily costs 10x what the Elixir app costs. Those are numbers that even the business sided folks love.
Once you have people that can develop in Elixir - the savings will easily show themselves in speed of development over time (code complexity) and server costs. Especially as the ecosystem matures with more packages.
8
Ninigi
I hear you there… The company I work for has become an elixir focused company now, but it took some work. We are mainly doing Shopify apps, so me being involved in your project helped a lot, and recently I was the proud merger of our elixir juniors PR. It was a tiny PR, maybe a si for line of code, but that’s how you get started!
I pitched the idea to make some of our internal solutions open source just today, but it’s always an uphill battle…
Is there even a user base for the phoenixe-shopify generator I am thinking of? Would anyone want to try use the graphql endpoint with ecto changesets? And many more things.
I will keep going in that direction, but sometimes I doubt myself and everyone… A little reassurance is greatly appreciated 
4
keathley
The desire to see other libraries gain momentum is often met with this exact response. And thats exactly the problem that people are mentioning in this thread. This isn’t to say I don’t like those libraries because I do. I use them every day and I’m happy. But saying that theres nothing to be gained by exploring other ideas is exactly the kind of mentality that I personally find very frustrating.
22
paulsullivanjr
Completely agree with this statement. Ecosystems evolve over time and additional libraries gaining momentum are part of that evolution.
2