4 ms·

So .7% tests fail therefor it was 100% a waste of time?

fg137 4mo ago
I think we are talking about ROI in terms of solving real world problems and making real impact, not the fact that a tool has been ported from language X to language Y.
Zopieux 4mo ago
Regardless, what's the point?
- tonymet 4mo ago
  maybe it's an academic project. proof they could reimplement something useful & complex?
- sharkjacobs 4mo ago
  > One of the main things I would like to be able to use it for is to be able to bundle complex push/fetch functionality into GitButler and other standalone Git tools needing network functionality (such as Jujutsu). > Having parts of Git as discrete, embeddable slices of library also enables things like building custom Git servers or client functionality in Rust. > The full build of all Git functionality in Rust is currently around 27M, but since a large part of it is a library, it could clearly be easily split up into domains of functionality - subcrates that do specific things. Perhaps you could simply use the subset you need.
- insanitybit 4mo ago
  The article starts out with paragraphs about the history and motivation. > it made me wonder about the feasibility of using that same approach to accomplish something I've been dreaming about for 15 years now, > which means that it's difficult to use it in long running processes without fork/exec overhead for everything. > What if we used the same basic idea that Anthropic used on their from-scratch C compiler? Start a brand new implementation, design it as a Rust library, then throw a swarm of agents at the problem
rvz 4mo ago
Given the author already admitted that the implementation was slow anyway, you are no better off of using gitoxide instead and that has support for Windows where-as Grit does not.
- sharkjacobs 4mo ago
  > Currently both Gitoxide and libgit2's networking functionality is either partial, slow or non-existant. Both GitButler and Jujutsu rely on forking out to Git in order to push or pull data. A big reason for this is the incredibly complicated credential logic involved, but all of this is (theoretically) currently covered in Grit.

fg137 4mo ago

I think we are talking about ROI in terms of solving real world problems and making real impact, not the fact that a tool has been ported from language X to language Y.

Zopieux 4mo ago

Regardless, what's the point?

tonymet 4mo ago
maybe it's an academic project. proof they could reimplement something useful & complex?
sharkjacobs 4mo ago
> One of the main things I would like to be able to use it for is to be able to bundle complex push/fetch functionality into GitButler and other standalone Git tools needing network functionality (such as Jujutsu). > Having parts of Git as discrete, embeddable slices of library also enables things like building custom Git servers or client functionality in Rust. > The full build of all Git functionality in Rust is currently around 27M, but since a large part of it is a library, it could clearly be easily split up into domains of functionality - subcrates that do specific things. Perhaps you could simply use the subset you need.
insanitybit 4mo ago
The article starts out with paragraphs about the history and motivation. > it made me wonder about the feasibility of using that same approach to accomplish something I've been dreaming about for 15 years now, > which means that it's difficult to use it in long running processes without fork/exec overhead for everything. > What if we used the same basic idea that Anthropic used on their from-scratch C compiler? Start a brand new implementation, design it as a Rust library, then throw a swarm of agents at the problem

rvz 4mo ago

Given the author already admitted that the implementation was slow anyway, you are no better off of using gitoxide instead and that has support for Windows where-as Grit does not.

sharkjacobs 4mo ago
> Currently both Gitoxide and libgit2's networking functionality is either partial, slow or non-existant. Both GitButler and Jujutsu rely on forking out to Git in order to push or pull data. A big reason for this is the incredibly complicated credential logic involved, but all of this is (theoretically) currently covered in Grit.