4 ms·
> Take a look at filesizes. The biggest files usually contain the meat of the program, or at least a dispatcher that points to the meat of the program. main.cc
by Stratoscope 9y ago
> Take a look at filesizes. The biggest files usually contain the meat of the program, or at least a dispatcher that points to the meat of the program. main.cc is usually tiny and useless for finding your way around.
This is my #1 pet peeve with GitHub. When I first look at an unfamiliar repo, I want to get a sense of what the code is about and what it looks like. The way I do that with a local project is by looking at the largest files first. But GitHub loves their clean uncluttered interface so much, they won't show me the file sizes!
- tome 9y agoYes, absolutely! I really want a whole-repo tree view of files along with their sizes and file types.
- tlapuste 9y agohttps://chrome.google.com/webstore/detail/octotree/bkhaagjahfmjljalopjnoealnfndnagc https://chrome.google.com/webstore/detail/octotree/bkhaagjah... Check out Octotree if you're using Chrome. No file sizes still, but I've found that when you just want to quickly explore some potential new source this beats having to clone the repo first.
- Stratoscope 9y agoThat is great, thanks!
- arocks 9y agohttps://chrome.google.com/webstore/detail/github-repository-size/apnjnioapinblneaedefcnopcjepgkci https://chrome.google.com/webstore/detail/github-repository-... I think this Chrome extension called "GitHub Repository Size" might be exactly what you are looking for
- Stratoscope 9y agoNice, thanks!