Ted Nyman – High Performance Git
gnabgib
77 points
12 comments
April 28, 2026
Related Discussions
Found 5 related stories in 1277.5ms across 14,015 title embeddings via pgvector HNSW
- Highlights from Git 2.54 ingve · 11 pts · April 20, 2026 · 57% similar
- Show HN: Gitdot – a better GitHub. Open-source, written in Rust baepaul · 206 pts · June 08, 2026 · 55% similar
- The Git history command deserves more attention turbocon · 179 pts · July 14, 2026 · 54% similar
- GNOME GitLab Git traffic caching JNRowe · 26 pts · April 18, 2026 · 54% similar
- Grit: Rewriting Git in Rust with agents cbrewster · 113 pts · June 09, 2026 · 54% similar
Discussion Highlights (5 comments)
wadefletch
ted nyman: #1 most knowledgable college football fan in sf and also git which makes more sense i guess
snthpy
I've been wanting to ask this: Why isn't git clone --depth 1 ... the default? I would guess that for at least 90% of the repos I clone, I just want to install something. Even for the rest, I might hack on the code but seldom look into the history. If I do then I could do a `git fetch` at that point and save the bandwidth and disk space the rest of the time.
normie3000
> LFS adds its own operational overhead. Seemingly seconds on every remote-touching command, even on a very small repo.
raphinou
Perfect read for the project I'm working on, which uses git as an auditable backend storage! (The project is an open source multisig signoff solution: all multisig definitions and signatures collected are stored in a git repo you can clone, see https://asfaload.com/ )
anitil
I'm only on to chapter two and already it's explained some plumbing details that I somehow have missed all these years. This is great