As someone who has deployed 4 apps through edeliver over 2 years, I have no idea what you are talking about, and I consider that a good thing. I had to update elixir and the deploy file slightly, but it was a lot smoother than expected!
Updating rails usually turns out to be a major issue, Phoenix was a breez, taking less than 5 hours to figure it out.
Would I choose Phoenix over rails again? Depends on the Developer, but I feel a lot more confortable and productive in Phoenix now.
This is a great point!
As a community, I feel we could definitely improve in being less critical of the alternative libraries. It’s clear that a new lib is not as mature as the established ones, but it still might be interesting because of the ideas brought to the table. We should focus on those ideas.
To aid in this process, I think that the authors of new libraries entering the charted space should clearly explain the new ideas and approaches they’re trying to introduce. To me, that’s even more important than having full-blown docs and getting-started guides. My advice to lib authors is to include a rationale doc in their project, and link to it at the top of the main readme, and the official announcement. As an example, see the second sentence, of my Parent readme.
In keeping with “attempting at empathizing with the other point of view”.
The way I see it, part of that mentality is fuelled by what has happened to the npm ecosystem.
Small modules: it’s not quite that simple:
I offer an additional explanation: that we in the JavaScript world have a higher tolerance for nonsense and dreck.
Some people simply don’t want the Elixir ecosystem to go down that road. It’s one thing to put whitebox (but not necessarily generalized) solutions on GitHub/GitLab that everyone can learn from (i.e. exploring other ideas). It’s another to potentially flood Hex with packages for the sake of someone wanting to have a package on Hex.
I actually see the problem in the reverse. Once you accept the prevalence of k8s (and/or Docker) it seems to undercut the perceived runtime value proposition that the BEAM can bring, for example in terms of fault tolerance.
How do your sell the BEAM to an established k8s/Docker shop? Seems to me they treat everything inside a deployment unit as an implementation detail where they just rather stick to established, “good enough”, mainstream technologies.
I have moved away from Elixir partly. My company has elixir as main software for the administration tools we develop. I do join in coding from time to time but its getting more rare as I move away from web services .
I am and always will be a c and c++ guy at my core because unlearning 22 years of bad habits is hard. that said elixir is really fun to work with.
If you read closely you’ll see that I asked a question and didn’t make a statement – I never said that there is nothing to be gained by exploring other ideas. I am still genuinely interested in the answer of my question which was “what is to be gained exactly?”.
I will again ask where do you see hostility?
We can’t have a dialog if you guys immediately feel frustrated and make sweeping generalizations. That’s not how a constructive discussion happens.
I asked a few questions in my earlier post and I didn’t get a single answer yet. I only get categorized as hostile. I find that quite puzzling.
As far as I am concerned, assuming intentions without a real dialog is the problem between these two supposed camps of people. Not any perceived hostility – which I am yet to see anywhere on this forum.
I was excited to see your Gleam project on Github. How is that progressing? Are you using it in production at all?
My experience was incredibly similar, started learning Elixir a handful of years ago, then got into some funemployment (with freelancing sidework) after moving to Asia for romantic reasons and took the opportunity to get really serious about Elixir. I also joined a startup over here that did not fare well, then joined a budding organization, made a small non-essential web app with Elixir on Phoenix, and now I lead a team building a more complex web system with Elixir / Phoenix.
Was easy to make the argument for doing a project in Elixir because the other teams here are primarily PHP (lotta PHP in this city…), and Elixir/Phoenix have really matured in the past couple of years IMO
Haven’t moved away from Elixir and likely won’t anytime soon, it is an amazing ecosystem for building resilient, flexible, fast APIs. I don’t miss Node/Ruby/PHP et al. at all
