[simonw]

SQLite does it despite using Fossil - their mirror is at https://github.com/sqlite/sqlite

Git is so established now that it's sensible for alternative VCS to have a mode where they can imitate the Git protocol - or seven without that you can still checkout the latest version of your repo and git push that on a periodic basis.

[adastra22]

Git is not a protocol, it is a data format. That only makes sense when your VCS system is similar enough to git to easily allow converting between the two representations.

[simonw]

I mean things like git-svn, hg-git, git-p4, git-remote-fossil, git-tfs, jj.

[adastra22]

Every single one of those is following variations on the exact same data structure, or is actually git in a trenchcoat.

[verdverm]

Similarly, CUE uses Gerrit and has two way sync. If you are building a VCS today, git interop is a must.

[adastra22]

What if the whole point of your VCS is that it its core data structure is nothing like git's at all?

[verdverm]

As a user, why do I care how the internals work?

What I do care about is an easy path to progressive adoption and migration. Without that, I cannot convince my team / org to force everyone over.

[adastra22]

It solves problems that you dont encounter if you are asking that question. I’ve lost a literal year or more of my life, in aggregate, to rebasing changes against upstream that could have been handled automatically by a sufficiently smart VCS.

[verdverm]

An alternative explanation is that I already have a tool that helps me with these situations. The question was a bit rhetorical, because the vast majority of devs don't care what language many of their tools are written in or what algos are used.

A different example, Go's MVS algo can be considered much better for dependency management. What are your thoughts on the SAT solver being replaced in your preferred language tooling? It would mean the end of lock files

[adastra22]

If you have a tool for better rebasing, I’d love to hear it.