3 ms·
I wouldn’t hold my breath. The scope of Git is quite large and Git-Oxide is just getting started. What I’d like to see is the Git core team adopt Rust gradually
by ironmagma 4y ago
I wouldn’t hold my breath. The scope of Git is quite large and Git-Oxide is just getting started. What I’d like to see is the Git core team adopt Rust gradually for certain subprograms.
- johnny22 4y agothat would fit how git itself evolved. A fair amount of code was in perl and stayed that way for awhile before being written in C.
- cerved 4y agomany of the porcelain commands are or used to be in perl/bash
- deleted 4y ago[deleted]
- kibwen 4y agoI don't know how far he intends to take it, but the author of gitoxide (which is just a library, like libgit2) uses it to power a git CLI called gix. As of October it looks like it can do fetches and clones: https://github.com/Byron/gitoxide/discussions/623 https://github.com/Byron/gitoxide/discussions/623 . Since the git CLI is subcommand-based, it wouldn't be too hard to provide replacements for individual git subcommands one at a time. If you replaced git clone, push, pull, commit, checkout, and rebase, that would suffice for 95% of git invocations.