4 ms·

Not sure what gitoxide is, but libgit already exists, and it seems to be an independent implementation - https://github.com/libgit2/libgit2 https://github.com/l

by chubot 1y ago

Not sure what gitoxide is, but libgit already exists, and it seems to be an independent implementation - https://github.com/libgit2/libgit2 https://github.com/libgit2/libgit2 I think Github and most big Git hosts use it

steveklabnik 1y ago
libgit2 has a ton of compatibility issues, especially around authentication, that make it only useful in some circumstances. (gitoxide is a similar project but in Rust, it's not ready for the big time either, though it keeps on getting better!)
- chubot 1y ago
  If it's about auth, then I'd say that's more about the "edges" / porcelain than the core. The claim about git is that you can re-implement the core data structures pretty easily, and they are stable While new functionality can be implemented on top of this stable base. It doesn't surprise me that it's hard to re-implement all of git, including the network protocols, but that's a different thing than the core This thread has some good info about the core, including the tree encoding issue brought up by bradfitz, but it still seems to be approximately true ... e.g. perhaps compared to hg I also remember that JGit is a very complete re-implementation of git, done by a git core dev, and used in Android infrastructure, etc. This was well over 10 years ago at this point, maybe 15 https://github.com/eclipse-jgit/jgit https://github.com/eclipse-jgit/jgit
  - steveklabnik 1y ago
    Yes, I think that the core is much better, all I mean to say is that 100% compat is difficult.
3eb7988a1663 1y ago
Jujitsu threw in the towel and is shelling out to the git CLI because of minor variations in libgit vs the binary. Failing to find a write-up, but there was this lobster thread[0] where someone from GitLab reported they had to do the same owing to some discrepancies vs the binary -where all of the real development happens. [0] https://lobste.rs/s/vmdggh/jujutsu_v0_30_0_released https://lobste.rs/s/vmdggh/jujutsu_v0_30_0_released
- Dylan16807 1y ago
  But nothing in that description of problems is tied to the repository format.

by chubot 1y ago

steveklabnik 1y ago

libgit2 has a ton of compatibility issues, especially around authentication, that make it only useful in some circumstances. (gitoxide is a similar project but in Rust, it's not ready for the big time either, though it keeps on getting better!)

chubot 1y ago
If it's about auth, then I'd say that's more about the "edges" / porcelain than the core. The claim about git is that you can re-implement the core data structures pretty easily, and they are stable While new functionality can be implemented on top of this stable base. It doesn't surprise me that it's hard to re-implement all of git, including the network protocols, but that's a different thing than the core This thread has some good info about the core, including the tree encoding issue brought up by bradfitz, but it still seems to be approximately true ... e.g. perhaps compared to hg I also remember that JGit is a very complete re-implementation of git, done by a git core dev, and used in Android infrastructure, etc. This was well over 10 years ago at this point, maybe 15 https://github.com/eclipse-jgit/jgit https://github.com/eclipse-jgit/jgit
- steveklabnik 1y ago
  Yes, I think that the core is much better, all I mean to say is that 100% compat is difficult.

3eb7988a1663 1y ago

Jujitsu threw in the towel and is shelling out to the git CLI because of minor variations in libgit vs the binary. Failing to find a write-up, but there was this lobster thread[0] where someone from GitLab reported they had to do the same owing to some discrepancies vs the binary -where all of the real development happens. [0] https://lobste.rs/s/vmdggh/jujutsu_v0_30_0_released https://lobste.rs/s/vmdggh/jujutsu_v0_30_0_released

Dylan16807 1y ago
But nothing in that description of problems is tied to the repository format.