Could it be simple and desirable to add some more metrics to the table? (download count, rating)

[Wizek]

I'm thinking about this because I am looking at https://packdeps.haskellers.com/reverse/hint to try to see which other packages built on top of it, and if one of them could have some specific features that I am looking for at the moment.

Currently I might have to open and read all 55 of them one after the other.

If, however, the table included 'download count in the last 30 days', then I could easily sort that table in my browser with a tampermonkey userscript (written for sorting tables on any site), and go investigate them one by one, starting from most used. Which could allow for 2 more desirable 'early-terminations':

• I either find what I am looking for in the form of a well-used package early on,
• or half-way through I already conclude that even if I would find the desired feature in one of the next packages, hypothetically them having 5 or less downloads in the last month is less than what I would feel justified using.

Same deal with the new(?) 0-3 hackage rating system, which may become even more relevant as more votes are cast. Downloads total could also be interesting to include if it's not too much trouble.

@snoyberg, what do you think about this change? And perhaps if your thoughts start in the direction of this being outside of the scope of packdeps, perhaps you could think of some other, better way with which I could achieve what I am after?

Edit: For this specific hint case I've gone with opening all of them manually and skimming through their descriptions. It surprisingly didn't take too much time in the end, and I could somewhat definitively determine that none of those packages were doing what I was looking for. However, this feature might still make sense for making this a workable avenue to explore packages, especially if there are hundreds of packages to look at.

[snoyberg]

I don't want to include the download counts, since they are known to be unreliable, both for to CDN usage, and since Stack downloads from a different source. I'm also not particularly interested in the new golden lambda rating system.

…

On Mon, Jan 15, 2018, 12:03 PM Milán Nagy ***@***.***> wrote: I'm thinking about this because I am looking at https://packdeps.haskellers.com/reverse/hint to try to see which other packages built on top of it, and if one of them could have some specific features that I am looking for at the moment. Currently I might have to open and read all 55 of them one after the other. If, however, the table included 'download count in the last 30 days', then I could easily sort that table in my browser with a tampermonkey userscript (written for sorting tables on any site), and go investigate them one by one, starting from most used. Which could allow for 2 more desirable 'early-terminations': - I either find what I am looking for in the form of a well-used package early on, - or half-way through I already conclude that even if I would find the desired feature in one of the next packages, hypothetically them having 5 or less downloads in the last month is less than what I would feel justified using. Same deal with the new(?) 0-3 hackage rating system, which may become even more relevant as more votes are cast. Downloads total could also be interesting to include if it's not too much trouble. @snoyberg <https://github.com/snoyberg>, what do you think about this change? And perhaps if your thoughts start in the direction of this being outside of the scope of packdeps, perhaps you could think of some other, better way with which I could achieve what I am after? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBB0rY9astrC4DunnKeJp0BNArQgSkks5tKyJmgaJpZM4ReLAS> .