GitDiagram
Dev tools
code visualization
SHOW HN2024
How HN took it
11 positive, 9 neutral or asking, 6 mixed, 21 critical, out of 47 comments about the project. Thread score -0.13.
Execution: 1 for, 10 againstIdea: 5 for, 2 againstDesign: 1 for, 3 againstPerformance: 0 for, 4 againstPricing: 0 for, 2 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Diagrams look accurate and useful at a high level
From 3 comments
As the author of the repo I was surprised how close to my mental model the graph was. (I haven't worked on this repo in a while so my mental model is a bit fuzzy) And yeah it…
lor_louis on HNHashicorp Vault (had to use my own API key as the repo is fairly large): https://gitdiagram.com/hashicorp/vault Diagram could maybe have a bit more detail but what is there looks…
nulld3v on HNghostty is sick, and the diagram seems accurate on a higher level
ahmedkhaleel on HN
Good idea for learning codebases faster
From 3 comments
I learn faster with visualization, whether it's a stat or a codebase. Much appreciated!
shahzaibmushtaq on HNI tried it on one of my repos and was somewhat impressed. I'd like to be able to drill down into subsystems though. This sort of tool could help to learn about codebases faster.
jasfi on HNThis is the neatest and most useful thing Shown on HN using AI in recent memory. Well done!
Jerrrry on HN
Objections
Repositories over 200k tokens fail, so large projects like Linux and llvm cannot be diagrammed
From 3 comments
Of course I have to test it with https://gitdiagram.com/torvalds/linux "Estimated cost: $8.07 USD" lol Edit: "Repository is too large (>200k tokens) for analysis. Claude 3.5…
uncomplexity_ on HNInputted llvm-project, resulted in this error: ``` Repository is too large (>200k tokens) for analysis. Claude 3.5 Sonnet's max context length is 200k tokens. Current size:…
owenpalmer on HNFinal boss: https://github.com/torvalds/linux Error message: Repository is too large (>200k tokens) for analysis. Claude 3.5 Sonnet's max context length is 200k tokens. Current…
Minervaskell on HN
Diagrams miss or wrongly show dependencies between components
From 2 comments
I guess to get the discussion going: the diagrams look nice, but I think the erroneous and missed connections limit their usefulness. In this example, there is a connection from…
billyp-rva on HNNice. I put in a repository of mine that implements a UI in Rust, and it gave me a reasonable diagram. It's just a top-level structure of the program, though. No detail. Not much…
Animats on HN
Generation often hangs or fails with generic progress messages
From 3 comments
Note: the messages that are displayed during diagram generation seem to describe the current progress - but actually they are generic/comedic messages that run in an endless…
thih9 on HNI tried this with a larger project, and after looping through the obviously-fake progress messages for a couple of minutes, it resulted in “Failed to generate diagram. Please try…
layer8 on HNTried https://github.com/scallyw4g/bonsai and I believe it hung after the green loading bar completed. Left it for several minutes
jesse__ on HN
Requests
Support for private repositories
From 1 comment
Looks great, but would love to see it work with Private Repos.
abrookewood on HN
Zoom controls and drill-down into subsystems
From 2 comments
Love what you've built OP Quick thought: Since you're tackling large codebases, maybe add some zoom controls?
k0ns0l on HNI tried it on one of my repos and was somewhat impressed. I'd like to be able to drill down into subsystems though. This sort of tool could help to learn about codebases faster.
jasfi on HN
Use of source code, not only README and file tree
From 1 comment
That’s very cool! Does it use the source code at all? Or does it just use README and directory tree?
phoenixreader on HN
Questions
Why large repositories fail given the stated goal of massive codebases
From 1 comment
>I created this because I wanted to contribute to open-source projects but quickly realized their codebases are too massive for me to dig through manually I don't get this…
gloosx on HN
Whether the tool uses source code or only the README and directory tree
From 1 comment
That’s very cool! Does it use the source code at all? Or does it just use README and directory tree?
phoenixreader on HN
Alternatives named
GitIngest
From 1 comment
Ilograph
From 1 comment
Didn't get a response (expected), but I would caution everyone to keep expectations low. Generating system diagrams from code is extremely difficult, if not impossible, even with…
billyp-rva on HN