Grace
git
Grace | git | |
---|---|---|
4 | 10 | |
502 | 730 | |
- | 2.1% | |
8.7 | 0.0 | |
about 1 month ago | 7 days ago | |
F# | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Grace
- Grace Version Control System
-
Ask HN: Can we do better than Git for version control?
There actually is a similar project in F#: https://github.com/ScottArbeit/Grace
git
-
Ask HN: Can we do better than Git for version control?
Microsoft had a bunch of solutions to handle their massive Windows repo: VFS for Git (GVFS), Scalar, and now it has a bunch of MS specific patches on top of the official git client, but apparently that one is also not required any more as partial clone is now supported on azure as well (which is another such implementation from Microsoft employees that made it to both GitHub and upstream git).
https://github.blog/2020-01-17-bring-your-monorepo-down-to-s...
https://devblogs.microsoft.com/devops/introducing-scalar/
https://github.com/microsoft/git
https://devblogs.microsoft.com/devops/git-partial-clone-now-...
-
We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
That was discontinued (like multiple times under different names). And is moved into a git fork. https://github.com/microsoft/git
- How to convince management that something like Git is industry standard?
-
Improve Git monorepo performance with a file system monitor
Interesting! It seems some of Scalar from late 2021 has already made it into the official git project's contrib dir [0]. It looks like Scalar is mostly an opinionated way to configure git [1], especially by using git partial-clone.
Git partial-clone looks almost perfect, except it only downloads and displays files explicitly added to the git sparse-checkout list. I want some "magic" vfs shenanigans that lets me view and browse the full repo exactly as if the full repo where checked out, but when I open a directory or file the contents are downloaded on-demand.
[0]: https://github.com/git/git/tree/master/contrib/scalar
[1]: https://github.com/microsoft/git/blob/vfs-2.37.0/Documentati...
-
GitHub incident: 2022/03/24
Ironically, Microsoft has been a major contributor to improvements in git for handling large repos after Windows was migrated to git.
https://github.com/microsoft/git
-
The largest Git repo on the planet (2017)
300GB git repo... anyway, good to see there's work for merge in back to git proper, though it seems like that is still a work in progress (maybe) as https://github.com/Microsoft/git/ still seems pretty active.
-
Make your monorepo feel small with Git’s sparse index
This is well written and deserves my upvote, because sparse-checkout is part of git and knowing how it works is useful.
That said, there's absolutely no reason to structure your code in a monorepo.
Here's what I think GitHub is doing:
1) Encourage monorepo adoption
2) Build tooling for monorepos
3) Selling tooling to developers stranded in monorepos
Microsoft, which owns GitHub, created the microsoft/git fork linked in the article, and they explain their justification here: https://github.com/microsoft/git#why-is-this-fork-needed
> Well, because Git is a distributed version control system, each Git repository has a copy of all files in the entire history. As large repositories, aka monorepos grow, Git can struggle to manage all that data. As Git commands like status and fetch get slower, developers stop waiting and start switching context. And context switches harm developer productivity.
I believe that Google's brand is so big that it led to this mass cognitive dissonance, which is being exploited by GitHub.
To be clear, here are the two ideas in conflict:
* Git is decentralized and fast, and Google famously doesn't use it.
* Companies want to use "industry standard" tech, and Google is the standard for success.
Now apply those observations to a world where your engineers only use "git".
The result is market demand to misuse git for monorepos, which Microsoft is pouring huge amounts of resources into enabling via GitHub.
It makes great sense that GitHub wants to lean into this. More centralization and being more reliant on GitHub's custom tooling is obviously better for GitHub.
It just so happens that GitHub is building tools to enable monorepos, essentially normalizing their usage.
Then GitHub can sell tools to deal with your enormous monorepo, because your traditional tools will feel slow and worse than GitHub's tools.
In other words, GitHub is propping up the failed monorepo idea as a strategy to get people in the pipeline for things like CodeSpaces: https://github.com/features/codespaces
Because if you have 100 projects and they're all separate, you can do development locally for each and it's fast and sensible. But if all your projects are in one repo, the tools grind to a halt, and suddenly you need to buy a solution that just works to meet your business goals.
-
Gitfs: Version Controlled File System
VFS for Git was superceded by https://github.com/microsoft/scalar and then many of the features were merged into mainline git, so what is left now is a thin shell around git features in the form of MS's forked git binary: https://github.com/microsoft/git
What are some alternatives?
oxen-release - Lightning fast data version control system for structured and unstructured machine learning datasets. We aim to make versioning datasets as easy as versioning code.
gitfs - Version controlled file system
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
VFSForGit - Virtual File System for Git: Enable Git at Enterprise Scale
fvim - Cross platform Neovim front-end UI, built with F# + Avalonia
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
Suave.IO - Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
mvfs - ClearCase file system
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
libgit2 - A cross-platform, linkable library implementation of Git that you can use in your application.
Paket - A dependency manager for .NET with support for NuGet packages and Git repositories.
git-fs - fuse + libgit2