VFSForGit

Virtual File System for Git: Enable Git at Enterprise Scale (by microsoft)

VFSForGit Alternatives

Similar projects and alternatives to VFSForGit

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better VFSForGit alternative or higher similarity.

VFSForGit reviews and mentions

Posts with mentions or reviews of VFSForGit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-02.
  • Debian Git Monorepo
    4 projects | news.ycombinator.com | 2 Apr 2024
    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

  • Serving a Website from a Git Repo Without Cloning It
    5 projects | news.ycombinator.com | 18 Feb 2024
    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

  • We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
    4 projects | news.ycombinator.com | 28 Aug 2023
    VFS for Git is still Open Source: https://github.com/microsoft/VFSForGit

    Microsoft's blog posts have indicated a move to use something as close to off-the-shelf git as possible, though. They say they've stopped using VFS much and are instead more often relying on sparse checkouts. They've upstreamed a lot of patches into git itself, and maintain their own git fork but the fork distance is generally shrinking as those patches upstream.

  • Why SQLite Does Not Use Git
    13 projects | news.ycombinator.com | 22 Jul 2023
    https://github.com/microsoft/VFSForGit

    better than it used to, with the caveat that git in particular is not and has never claimed to be good at versioning blobs.

  • ๐Ÿ‚ ๐ŸŒพ Oxen.ai - Blazing Fast Unstructured Data Version Control, built in Rust
    5 projects | /r/rust | 16 Feb 2023
    Oh dear you're not going to like this.
  • He is very conservative...
    2 projects | /r/ProgrammerHumor | 3 Feb 2023
    Itโ€™s virtualised file system: https://github.com/microsoft/VFSForGit, only downloads what you actually use. Same thing in every large company, but different implementations.
  • FYI: LLVM-project repo has exceeded GitHub upload size limit
    7 projects | news.ycombinator.com | 30 Jan 2023
    This is where something like VFSForGit[0] helps out. Instead of cloning the entire repo, it creates a virtual file system and fetches objects on demand. MSFT uses it internally for the Windows source tree (which now exceeds 300GB).

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

  • Created a Small Program To Display Upcoming Assignments On My Desktop
    3 projects | /r/csharp | 28 Jan 2023
    There's also a performance consideration. Not excluding /bin/ or /obj/ folders means dependencies are being tracked as well, and sometimes dependencies themselves are bigger than the program's source code itself. This is commonly the case with node projects, as the node_modules folder can balloon to hundreds of megabytes. They should never be tracked in git due to the nature of how git's internal database works. For e.g. if you delete a dependency because it's no longer needed, you can never fully reclaim that disk space (at least for the master branch) as git will need to keep the binary data stored in its internal tracking database because a previous commit in the master branch has captured the data. As you make more branches, git needs to store the data required to reconstruct your repo to a different state when you switch branches. When a branch has changes measured in the kilobytes, check out is very manageable, but when the differences balloon to many MBs due to the presence of heavy binary files, then checkout between different branches/commits can get very slow. Though, this happens anyway when source code data eventually reaches a certain threshold, beyond the hundreds of megabytes, it's made unnecessarily worse by including any binary files. It's one of the reasons Microsoft created VFS for git: https://github.com/microsoft/VFSForGit.
  • Meta releases Sapling, a new way of using source control
    4 projects | /r/programming | 15 Nov 2022
  • Software for managing config files
    2 projects | /r/sysadmin | 22 Oct 2022
    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.
  • A note from our sponsor - WorkOS
    workos.com | 25 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more โ†’

Stats

Basic VFSForGit repo stats
24
5,938
4.7
about 1 month ago

microsoft/VFSForGit is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of VFSForGit is C#.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com