EdenSCM VS scalar

Kind of weird that https://github.com/facebookexperimental/eden (linked in mononoke) redirects to sapling. Does that mean it's replacing eden?

Maybe at their scale it makes more sense to switch to a VCS like Eden? https://github.com/facebookexperimental/eden

Eden's equivalent of 'git status' should run almost instantaneous, as checkouts are hosted by a virtual file system (FUSE) that tracks changes.

Meta having moved on from Mercurial may be a factually true comment, but it looks like they still have fondness for Mercurial's ways:

https://github.com/facebookexperimental/eden

> - A build system / package manager like Nix [1] but with a better user experience / more straightforward command-line tooling.

Working on it :)

> - A version control system which scales to petabytes or more. Something that I could put large video files in without thinking twice about it. Something a large company could use for their monorepo—or even their data warehouse.

https://github.com/facebookexperimental/eden

> A note-taking tool that allows me to organize notes in a graph with links between them

https://www.orgroam.com/

Eden - a cross-platform, scalable source control management system from Meta.

Eden\ (202 comments)

Meta open-sourced their complete stack: https://github.com/facebook/sapling

Microsoft released Scalar (https://github.com/microsoft/scalar) although it's not a complete stack yet but it is already planning on releasing the backend components eventually.

Have you tried Sapling?

It's not only Windows that uses Git at Microsoft, but Sharepoint and Office (which includes the on-prem version of SharePoint). In terms of repo size Windows and Office are similar. I was part of the team that migrated Sharepoint from a Perforce clone to Git and helped build the tooling to allow Office to move as well. VFS for Git [1] and Scalar [2] are really good pieces of software.

[1] - https://github.com/microsoft/VFSForGit

[2] - https://github.com/microsoft/scalar

Congratulations! That means you basically figured out how the clone procedure works and found a way to do so just in a partial way (also in an unsafe way). But it is a cool idea, nonetheless.

Also check out the Scalar [1] project and its predecessor, GVFS [2], both from Microsoft to manage their monorepo via a VFS layer.

[1]: https://github.com/microsoft/scalar

[2]: https://github.com/microsoft/VFSForGit

You mean like VFSforGit? Or the successor for that called Scalar? This has been a solved problem. Microsoft moved their entire Windows codebase to git. There have been a ton of huge improvements to performance as a result of that. And the above two plugins are easily better ways to deal with what you're referring to without resulting to dead tech.

I was just looking at Microsoft's git VFS (https://github.com/microsoft/VFSForGit), which is deprecated and now points to Scalar (https://github.com/microsoft/scalar), which is also deprecated? What's Microsoft's story with git now? Is there still a virtual file system involved?

Microsoft has/had a mono-repo based on the Git Virtual Filesystem, but future efforts have apparently moved towards the use of Scalar: https://github.com/microsoft/scalar

This has been superceded by Scalar (https://github.com/microsoft/scalar) and again merged into Microsoft's fork of git (https://github.com/microsoft/git)

It supports neat stuff like partial clone which seems like a pretty big deal.

As mentioned in the blog "we are moving towards providing a known version of git", probably Microsoft Git which includes the scalar command but also upstreams many of the optimizations to git core https://github.com/microsoft/scalar#why-did-scalar-move

disclaimer: canva staff working on source control