GitHut – Programming Languages and GitHub (2014) • Hacker News Board

I think correlating "pushes per repository" to certain languages is interesting. The top "pushes per repository" are C++, TeX, Rust, C, and CSS. I guess it's no surprise many would also consider those the most guess-and-check or hard-to-get-right-upfront-without-tooling languages too.

Re: GitHut – Programming Languages and GitHub (2014)

#6

Post by some_guy_nobel » Thu, Nov 20, 2025, 9:44 PM UTC

miguel_martin wrote: post #2

Why are Nim, Odin, Zig, Mojo not included (and probably many others)?

Probably because this was made in 2014 :D

Re: GitHut – Programming Languages and GitHub (2014)

#7

Post by [deleted] » Thu, Nov 20, 2025, 9:44 PM UTC

[deleted]

Re: GitHut – Programming Languages and GitHub (2014)

#8

Post by ivanjermakov » Thu, Nov 20, 2025, 9:45 PM UTC

Would be fun to weight each language by average number of stars, but normalize by repository count.

Data analysys without adjusting groups by popularity is a bit lame.

Re: GitHut – Programming Languages and GitHub (2014)

#9

Post by tonyhb » Thu, Nov 20, 2025, 10:11 PM UTC

jtwaleson wrote: post #3

Would love to see an update to 2025

I really, really want this updated too and saw it in my bookmarks. Figured the historic data was interesting, and that someone might want to give this another go.

Re: GitHut – Programming Languages and GitHub (2014)

#10

Post by ethmarks » Thu, Nov 20, 2025, 10:13 PM UTC

Absolutely stunning and ingenious visualization, but disappointing data. In 2014 there were 2.2 million repos, while in 2025 there are closer to 500 million. The repo was last updated seven years ago, so I assume that this project has been abandoned.

A cursory glance at the source code[1] reveals that it's using GitHub Archive data. Looking through the gharchive data[2], it seems like it was last updated in 2024. So there's 10 years of publicly accessible new data.

Is there any reason we (by "we" I mean "random members of the community" as opposed to the developer of the project) can't re-build GitHut with the new data, seeing as it's open source? It's only processing the repo metadata, meaning it shouldn't even be that much data and should be well under the free 1TB limit in BigQuery (The processed data from 2014 stored in the repo[3] is only 71MB in size, though I assume the 2024 data will be larger), so cost shouldn't be a concern.

I'm not experienced enough to know whether creating an updated version of this would take an afternoon or several weeks.

[1]: https://github.com/littleark/githut/

[2]: https://console.cloud.google.com/bigquery?project=githubarch...

[3]: https://github.com/littleark/githut/blob/master/server/data/...