Re: Git haas gone wild (Rust)

> On Sep 9, 2025, at 1:18 AM, Mark Liam Brown <brownmarkliam@gmail.com> wrote:
> 
> On Fri, Sep 5, 2025 at 6:42 PM Michael Osipov <michaelo@freebsd.org> wrote:
>> 
>> Folks,
>> 
>> you might want to enjoy or discuss:
>> https://lore.kernel.org/git/20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im/T/#t
>> 
> 
> Or switch to Mercurial, https://www.mercurial-scm.org/ and declare git
> as obsolete

	Community maintained hg doesn’t scale as well as git and never built up the external community support that’s present with hosted solutions like GitHub, gitlab, etc. The fact that large groups of the *OSS community settled on git a few years ago and MS bought GH was probably a large red flag that should have inspired other groups to consider alternatives to hosting purely git-based infrastructure. Maybe this will be the impetus for that change.
	I was told that Meta tried getting hg to scale some years ago with monorepos, but gave up working with the community since they weren’t moving quickly enough at the time (this was the “heavy” “move fast and break things” 2014~2016 period at FB) and forked/integrated a bunch of the stuff into arcanist (which eventually became “jellyfish”). git didn’t scale with their monorepo size/structure, which is why they didn’t adopt it. The fbcode monorepo at that time was similar in scale to FreeBSD—maybe an order of magnitude larger with some of the third-party components, but it was in the same general ballpark when I left in 2018. As a funny sidenote, I was told they switched from a C++ or python backend to a rust backend of their custom hg fork to help scale up the VCS right before I left.
Cheers,
-Enji