GitoxideLabs

gitoxide

Rust2020–2026

GitoxideLabs / gitoxide

gitoxide

A tasteful, lean, fast & safe pure Rust implementation of Git

Command Line Developer Tools

Explore on GitHub Read Hacker News discussions

23Distinct people

29Mentions

1Explicit recommenders

12.1KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A tasteful, lean, fast & safe pure Rust implementation of Git

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

As someone who has spent probably a percent or more of my life working on or thinking about state, and how it could or should just be decomposed 9p files when possible, about…

jauntywundrkind used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year29 dated mentions

Observed mentions: 2020-08-13 03:57:03 UTC to 2026-07-23 16:15:58 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	4	1	3
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	2	1	1
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	8	4	4
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	5	2	3
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	3	1	2
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	6	0	6

What Hacker News says

6 sources

yencabulator·Jul 23, 2026

JJ's use of the Git file format is done via https://github.com/GitoxideLabs/gitoxide -- there's still some missing features in the networking part, but the local-file-manipulation features are fully there.

In git's –end-of-options Flag

GreenDolphinSys·Jun 10, 2026

Yet, you didn't write the code yourself. On Gitoxide: Given that the author read the docs and source code [0], and literally copied files over from the git source [1], it also is license-washing. At least libgit2 is GPLv2 with a linking exception. I don't think people would have much to say if these projects honored the original projects' intents and kept a copyleft GPL license. But they don't. > The approach needed to make this a reentrant, memory safe, library driven codebase is so different that copying is generally not useful. This is obvious given how different Rust is from most languages. So are licenses pointless as a concept now, because anyone can argue their Rust implementation of a GPL (or whatever) project is meaningfully different? Nice loophole there. Stripping away the GPL in favor of MIT/ASL2.0 seems to be the trend for ru

Read the rest

st projects (see uutils, etc). I'm really glad that we can make it easier for large companies to extract value from community labor and, in general, not contribute much of anything back. 0: https://github.com/GitoxideLabs/gitoxide/discussions/253 1: https://github.com/GitoxideLabs/gitoxide/issues/925

In Grit: Rewriting Git in Rust with agents

schacon·Jun 10, 2026

As mentioned, we also work on the Gitoxide project and Byron is a member of our team. We are well aware of all large community efforts and we're also cohosting the Git Merge conference this year. There is a recent effort to vibe-loop more Git into Gitoxide, which is interesting: https://github.com/GitoxideLabs/gitoxide/pull/2538 I still think that this is a project that can have value with a little more work. This announcement is merely a milestone, not the end product. I wasn't sure it was really possible to do, even halfway through the project. There has been a lot learned and there is a lot to learn, but I think there are useful applications for both a high quality, hand crafted, opinionated partial Git library (Gix) as well as a vibed, fully implemented, partially sloppy LLM Git library (Grit). We think it's worth exploring and invest

Read the rest

ing in both options for now. Also, I am the exec involved and I've done quite a lot for the Git community over the years. I would never try to have my "own copy" of it, that's ridiculous. I wrote and open sourced the Pro Git book (https://git-scm.com/book/en/v2) and Git community book before it (https://schacon.github.io/gitbook/index.html), I created the official Git website (https://git-scm.com), I cofounded GitHub which hosts nearly all open source in the world, I have evangelized and supported the Git ecosystem for almost 20 years now. I restarted and funded development of libgit2 15 years ago, which you could similarly argue was an exec trying to have our "own copy" of Git under a more permissive license and would have been a similarly ridiculous argument.

In Grit: Rewriting Git in Rust with agents

boredatoms·Jun 9, 2026

Theres already git-in-rust project that is making good progress https://github.com/gitoxidelabs/gitoxide

In Grit: Rewriting Git in Rust with agents

jauntywundrkind·Apr 16, 2026Recommendation phrase

As someone who has spent probably a percent or more of my life working on or thinking about state, and how it could or should just be decomposed 9p files when possible, about externalizing state & opening up new frontiers of scripting, and how git can tie that together and let us build new distributed systems, I am cheering. Cheering wildly. The zig wasm sounds so so good. I've enjoyed git on rust via gitoxide ( https://github.com/gitoxidelabs/gitoxide ) but haven't tried wasm yet. I rather expect gitoxide/rust would be bigger. The ability to really control memory like they talk of here seems like it could be a huge advantage for wasm inter-op across a SharedArrayBuffer (or like) holding the code too. Rust seems unlikely to be able to offer that. The ArtifactFS fuse driver sounds wonderful. My LLM session to build an csi storage driver is

Read the rest

already begun! On another note, this gives me all kinds of feels: > Inside Cloudflare, we’re using Artifacts for our internal agents: automatically persisting the current state of the filesystem and the session history in a per-session Artifacts repo. On a personal level I find this amazing & incredible & I love it. But reciprocally this feels like an incredibly difficult social change. To collect all the work, to collectivize the thought processes / thought making. I am so enamoured with LLM programming. And I have so wanted engineering to better be able to externalize the tale of what happened, what did we do. But this also feels like there is no privacy, that this raw data is deeply deeply deeply personal. I feel so so so good about this & so scared too. I want very much to work more in public, but I also want some refuse, some space of my own. We lost offices for cubicles, and now we lose the sanctity of our own screens too? I both want to share, so much, to have shared means of thinking, but via more consensual deliberate means, please.

In Artifacts: Versioned storage that speaks Git

SAI_Peregrinus·Mar 30, 2026

JJ doesn't directly touch the `.git` directory, it uses gitoxide¹ to perform git operations. ¹https://github.com/GitoxideLabs/gitoxide

In More on Version Control