You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if an issue is the right place for this but I don't think the godoc.org count is really comparable to any of the other indices you have up there. godoc.org is essentially a list of all the modules in all the go repos on bitbucket and github. PyPi, CPAN, NuGet and all the others require an author to do at least minimal packaging and publishing for their module. Doing a quick sanity check shows that there are 437414 Python repos, 81006 Perl repos, compared to just 37434 Go repos on Github.
Don't get me wrong comparing github/bitbucket repo counts over time is valuable I just don't think we should comparing the repo counts of one language to the package counts of others. With a more CPU intensive scraping you could limit godoc.org count to modules which have at least one other module using them. You would only have to check it once for each new godoc.org module you see. A simple GET request per module is all that is needed.
The text was updated successfully, but these errors were encountered:
I am not sure if an issue is the right place for this but I don't think the godoc.org count is really comparable to any of the other indices you have up there. godoc.org is essentially a list of all the modules in all the go repos on bitbucket and github. PyPi, CPAN, NuGet and all the others require an author to do at least minimal packaging and publishing for their module. Doing a quick sanity check shows that there are 437414 Python repos, 81006 Perl repos, compared to just 37434 Go repos on Github.
Don't get me wrong comparing github/bitbucket repo counts over time is valuable I just don't think we should comparing the repo counts of one language to the package counts of others. With a more CPU intensive scraping you could limit godoc.org count to modules which have at least one other module using them. You would only have to check it once for each new godoc.org module you see. A simple GET request per module is all that is needed.
The text was updated successfully, but these errors were encountered: