LOL, this site is a joke. It’s just the Awesome Elixir repo README (not curated at all) which is parsed into a web page.
sotojuan
yordisprieto
Why you don’t take the idea and build it. Everyone agree on the fact that is an issue in our industry and at least that app is trying to fix it.
I encourage you to create something or just use the platform, giving feedback, using the ranking system, I don’t know but definitely something more than just laugh about it.
0
yordisprieto
this is the reason why I don’t believe on 100% freedom. This is why I prefer having seniors with a lot of experiences driving the community decisions.
I don’t believe on the freedom when I know ignorant people can screw a decision. I am ignorant enough for no be able rank correctly the packages because I don’t know that much about ErLang or Elixir.
I prefer to create a role (like seniors inside the community) that you have to gain the truth and respect for be able to be in that role.
I just want to see this issue to be fix. I bother me that we knowledge that is an issue and we don’t try to fix it.
0
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
My point wasn’t just that the site in question was doing a poor job. My point was also that Hex.pm is actually doing a very good job. If you search for a topic you get a relevant list of items, the description, and the downloads count which helps you figure out how much the community relies on the packages.
2
yordisprieto
Yes, and that’s why I don’t want to use something external and actually extend Hex.pm.
Like at least have a badge that said: Recommended by the community; or something similar.
0
Mandemus
For non curated lists that particular feature can cause problems down the road. Meteor had a similar aggregate for all packages with metrics (including a fancy graph widget.)
The problem arises when you as a new user see a package has 99e99 downloads only to find out that it’s been abandoned for two years. Well, hey it used to be popular!
1
PragTob
I guess in the end it’s a mixture of existing solutions that yields best results but requires some amount of research:
- total downloads
- recent downloads (love that hex provides those)
- README - aka what is this package good at, API etc.
- is there a Changelog?
- when was the last release?
- how long has the package been around
- github stars
- open issues
- open PRs
- recent commit activity
- blog posts
- what do my friends use…
In the end no one can take the tough decision of what library to use of your hands and responsibility.
I think 3rd party websites can help with this, so while libhunt.com fails to sort the search correctly I think it’s a good step. I liked ruby-toolbox a lot but it is broken for some time now…
That is always the problem, someone has to maintain lists and whatever. A particular problem I have with a “committee” is who decides what gets in and who’s on that committee. For instance in Ruby land the most interesting stuff happening imo is rom-rb, hanami and trailblazer. For all I know, dhh probably doesn’t like them very much and I also heard that they’re not that well known/highly regarded in the U.S. I also think it’d be great if they’d take their talents to other languages (like… Elixir) but that might just be me 
I agree that rather than creating new stuff working together to improve existing libraries is preferable, it’s not always possible though. Sometimes project philosophies just diverge too much or a better solution to a problem requires a wholly different approach and it’s easier to implement something new than make a backwards incompatible release of library X (like lots of people said Angular2 should have had a new framework name).
Sometimes breaks are needed and a new thing needs to come up. Like shrine in ruby for instance. Also after evaluating all other benchmarking libraries I could find in Elixir I decided to make my own (a dormant PR and low test coverage among others later though). It’s hard to gain traction for new things though…
2
Kabie
I think what hex could do better is providing more information, and let the user do their own decisions.
0
PragTob
Well, what information are you thinking about here? That’d be good to know in order to maybe turn it into actionable items
1
bobbypriambodo
Oh, I cannot express how important this point is. I remember times (mostly when dealing with npm packages) when I need to dig down for a changelog only to end up reading their raw commit history and diffs. It’s not a fun experience. Human-readable changelogs should be made mandatory, and failure of providing one should be considered a crime (okay, I’m exaggerating 
).
1