Awesome 
AstonJ
ericmj
Elixir Core Team
Hex.pm is adding support for multiple repositories but they will not be public except for the “global” one. But I think the issue is here is exactly the opposite, the people that want a curated package manager doesn’t want forks or alternatives to packages.
Module names are not enough to namespace against conflicts. You have to also change application names, process names, ets table names and a lot of other things. The VM wasn’t built to support multiple variants of the same application loaded at the same time.
2
josevalim
Creator of Elixir
This is the takeaway here. Asking for some sort of committee that will rank packages is like requesting someone else to do your job. How will this committee even be able to judge all packages that go into Hex about Phoenix, GraphQL, Databases, Elastic Search, Nerves, C extensions, etc? Each of those require specific domain knowledge.
Instead we need to discuss how to assess the health and quality of a project. README, documentation, usage, number of committers depending on the project size and if the team is responsive on new issues. Then there is a whole series of aspects related to your current domain: are the APIs well designed? Is the code tested? Does it use meta-programming only when absolutely necessary?
FWIW, I strongly dislike any measure that includes commit activity. What if the package is just… done?
9
yordisprieto
Probably that’s what I am trying to said from my frustration of watch how we follow the Ruby and/or NodeJS community path. Where you have literally one function package or duplicated work instead of work together.
I just want people to cooperate together instead of work separately. I just want a community where is not about diversity but instead something that works and it’s robust.
Every time you create a new package is like starting from 0. Diversity is good when there is a really good reason for it. In this case, faker vs ffaker is just somebody that wants to see the same set of gems in Elixir (No reason at at, and sorry call me rude but it’s true).
Why Engineers want to reinvent the wheel every time, why is so hard to cooperate as a team (even when we are not working in the same company).
@josevalim probably the only thing I am asking from the Core is to train the Elixir community about the topic … because nobody will listen to a nobody
And I has been doing my work, I do not come or ask anyone to do it for me, I has been updating this https://elixir.libhunt.com/ at least contributing to the categories sections because I didn’t use that much of packages (instead of writing a blog because writing is not my skill as you already know)
But you are right!
2
yordisprieto
Isn’t better to try to contribute to that package? (2 people thinking together instead of 1?!?!?) See wha the creator have to say about. Probably he will create a better documentation or change the core of the package?
From your example, just from the readme you need to catch up with that package, probably doc (I dont know) and many other things just because you started from 0
1
radar
Yes I would try to contribute but as I stated before, I felt the code was overengineered (quite the liberal use of macros) and the documentation sparse. I felt it would take me much longer to understand the code than it would to write a simple(r) implementation myself. I was right.
1
yordisprieto
radar
I didn’t explain my concerns because I didn’t think I could phrase them in a kind way. “Hey mate, your liberal use of macros scares/confuses me. Care to tidy it up or document it?”. I also noticed there were recent issues in the issue tracker which weren’t attended to and so if I filed one too then it would just be another issue on the pile of ignored issues.
What I wanted was some simple-to-understand Elixir code to communicate with Elastic Search. I didn’t find it after a cursory Google search, so I built my own. It was only later I discovered a similar project: GitHub - werbitzky/elastix: A simple Elasticsearch REST client written in Elixir. · GitHub
Since I’ve got my own version running in production now and don’t have any real reason to switch to elastix, I’m going to continue using/maintaining my own.
Maybe one day down the line the maintainer of elastix and I will agree that it makes sense that only one implementation like this exists and merge the ideas from our two projects into one, but for now it’s fine that they exist as two separate entities.
3
josevalim
Creator of Elixir
I agree with your reply. Communication is important and we should seek for collaboration. Elixir tries to lead by example here up to some extent when it comes to Erlang integration. Pushing developers to not simply wrap Erlang abstractions and contributing improvements, reporting bugs and more upstream whenever possible.
Btw, I didn’t want to imply you were not doing work. Although reading back I can clearly see how it can be read exactly as that. Sorry.
3