4 ms·

I wonder for the reason of all these list repos in the past few years. It would awesome if there was a better way to search repos. Maybe semantically in a way t

I wonder for the reason of all these list repos in the past few years. It would awesome if there was a better way to search repos. Maybe semantically in a way that you had a problem to solve and it would suggest open source projects. I think its cool to see lists of projects but I dont find it super helpful, am I supposed to bookmark 20 repos which each list another 1000 repos? There has to be a better way for discoverability.

kevinsundar 5y ago
It goes deeper haha https://github.com/bayandin/awesome-awesomeness https://github.com/bayandin/awesome-awesomeness https://github.com/sindresorhus/awesome https://github.com/sindresorhus/awesome
armchairhacker 5y ago
Wiki pages. A repo containing README.md is a primitive wiki page. And with GitHub you can contribute (pull requests) or discuss meta (issues). But a page on Wikipedia or something like it be better. But, it's harder to create such a wiki then a GitHub repo (which most devs are already familiar with). And it might not show up as high on SEO. So GitHub repo it is.
qbasic_forever 5y ago
Github still has atom feeds for repos, for example: https://github.com/rothgar/awesome-tuis/commits/master.atom https://github.com/rothgar/awesome-tuis/commits/master.atom Unfortunately they don't really make links to these feeds very visible in the UI anymore. But toss that in your feed reader of choice and you'll get an update when the awesome list content changes.
octoberfranklin 5y ago
> It would awesome if there was a better way to search repos. Not having that is kinda the whole value proposition of Big Data. Github gives you free bandwidth and disk space. In return they get to "grep like a boss" running complex queries with no fuzziness; you don't. Similar story with search engines and their crawler output. And Amazon's product catalog. None of these let you turn off the fuzziness and run large/frequent/complex queries, even if you're willing to pay for it. Amazon's "good" product search API is ratelimited by how many convertible leads you send them. I dunno, it's kinda lame, but I guess that's how things work.

kevinsundar 5y ago

It goes deeper haha https://github.com/bayandin/awesome-awesomeness https://github.com/bayandin/awesome-awesomeness https://github.com/sindresorhus/awesome https://github.com/sindresorhus/awesome

armchairhacker 5y ago

Wiki pages. A repo containing README.md is a primitive wiki page. And with GitHub you can contribute (pull requests) or discuss meta (issues). But a page on Wikipedia or something like it be better. But, it's harder to create such a wiki then a GitHub repo (which most devs are already familiar with). And it might not show up as high on SEO. So GitHub repo it is.

qbasic_forever 5y ago

Github still has atom feeds for repos, for example: https://github.com/rothgar/awesome-tuis/commits/master.atom https://github.com/rothgar/awesome-tuis/commits/master.atom Unfortunately they don't really make links to these feeds very visible in the UI anymore. But toss that in your feed reader of choice and you'll get an update when the awesome list content changes.

octoberfranklin 5y ago

> It would awesome if there was a better way to search repos. Not having that is kinda the whole value proposition of Big Data. Github gives you free bandwidth and disk space. In return they get to "grep like a boss" running complex queries with no fuzziness; you don't. Similar story with search engines and their crawler output. And Amazon's product catalog. None of these let you turn off the fuzziness and run large/frequent/complex queries, even if you're willing to pay for it. Amazon's "good" product search API is ratelimited by how many convertible leads you send them. I dunno, it's kinda lame, but I guess that's how things work.