EdenSCM – A cross-platform, scalable source control management system

Facebook rewrote Mercurial, while Microsoft has essentially expanded git with their own virtual file system VFSforGit [0] and a bunch of performance improvements.<p>0 - <a href="https:&#x2F;&#x2F;vfsforgit.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;vfsforgit.org&#x2F;</a>

BTW : with so many smart and connected people interested in source control management in one place, does anyone know what happened to veracity scm (<a href="http:&#x2F;&#x2F;veracity-scm.com" rel="nofollow">http:&#x2F;&#x2F;veracity-scm.com</a>)?<p>It was very promising but the suddenly stopped updating and then (more or less intentionally it seemed) links stopped working, but the site is still up 7 years later...

There is more tooling needed in general - just one recursive grep will populate the entire EdenFS.<p>I suppose FB has better tools. But I won’t touch this until the ecosystem is sufficient (and also, because git and hg are perfectly sufficient for the monorepo I oversee)

Interesting. This might be a step in the direction of being able to store big files in repositories without hassle.<p>However, perhaps OS level support would be preferred. Imagine you have a type of symbolic link that is not just followed, but executed when you access it. That would be really powerful and would allow this kind of optimization. And you wouldn&#x27;t even need to install or run anything.

Does this work together with a build cache? My dream setup for dealing with building huge code bases is a file system integrated with the version control system to only download files when they are accessed (which sounds like what this does) but also employing a build cache and module system, so it doesn&#x27;t even need to download and compile any module that has not been touched, it just downloads the result from the build cache instead.

&gt; A virtual filesystem for speeding up the performance of source control checkouts.<p>To describe it as a filesystem matches my thinking [0]: &quot;It already resembles a network file system, so it should provide an interface nearly as easy to use.&quot;<p>If it really takes off as an Open Source project, we might be able to &quot;mount&quot; repostories eventually.<p>[0] <a href="http:&#x2F;&#x2F;beza1e1.tuxen.de&#x2F;monorepo_vcs.html" rel="nofollow">http:&#x2F;&#x2F;beza1e1.tuxen.de&#x2F;monorepo_vcs.html</a>

If I were going to try something other than git, it would be fossil =&gt; <a href="https:&#x2F;&#x2F;fossil-scm.org&#x2F;home&#x2F;doc&#x2F;trunk&#x2F;www&#x2F;index.wiki" rel="nofollow">https:&#x2F;&#x2F;fossil-scm.org&#x2F;home&#x2F;doc&#x2F;trunk&#x2F;www&#x2F;index.wiki</a>

I think the one big differentiator for this is:<p>&quot;EdenSCM is not a distributed source control system. In order to support massive repositories, not all repository data is downloaded to the client system when checking out a repository&quot;