3 ms·
So many tools are tightly coupled to git or just assume that everybody uses git. I think that it's hard for any new VCS to gain traction without good git compat
by tcoff91 7mo ago
So many tools are tightly coupled to git or just assume that everybody uses git. I think that it's hard for any new VCS to gain traction without good git compatibility.
For instance Pijul might very well be a lot better than git / jj. I wouldn't know, I haven't bothered trying it because all the projects I need to work in use git. But since jj has great git compatibility, I actually have been able to adopt it because of its git backend.
A new VCS that doesn't have git compatibility at its core is going to have a really hard time overcoming network effects.
- collabs 7mo agoYou're talking about a new VCS but I don't know how even git with sha-256 will gain any traction because I don't see how you can support both...
- chriswarbo 7mo agoTooling can support both (e.g. don't assume all hashes have the length of a SHA1, etc.); but they can't be used together in one repo.
- esafak 7mo agoThe great thing about jj is that it is backend agnostic; it is the best gateway to newer version control systems.
- e40 7mo agoDoes jj write to the .git directory or use git’s libraries (I assume they exist)?
- SAI_Peregrinus 7mo agoJJ doesn't directly touch the `.git` directory, it uses gitoxide¹ to perform git operations. ¹https://github.com/GitoxideLabs/gitoxide https://github.com/GitoxideLabs/gitoxide