From: Collin Funk Date: Fri, 19 Sep 2025 18:14:54 GMT Subject: Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty Message-ID: <87segiqpgh.fsf@gmail.com> In-Reply-To: Ezekiel Newren writes: > On Fri, Sep 19, 2025 at 11:36 AM Sergey Fedorov > wrote: >> This will be a disaster, please consider not making rust mandatory. >> It will break git for all systems without rust, in effect killing not only possibility to use GitHub and other git-based services, but also breaking build systems, since many ports – and package managers – rely on git to fetch sources. >> As for local version control, git could be replaced with some alternative (likely inferior, but at least that is not the end). >> There is no replacement, AFAIK, for build systems and for git-based online services. >> >> P. S. In case anyone wonders, this is personally relevant for me: I won’t be able to continue contributing to open-source anymore (at least certainly not like in past years) with git being unusable due to broken rust. > > The mailing list has had extremely heated debates about this, and > there are many who would agree and disagree with you. So please try to > read my comment as a genuine interest in trying to understand your > situation. I would like to hear why making Rust mandatory would make > using and contributing to Git insurmountable. We know for sure that > NonStop currently does not support Rust at all, and that there are > problems with porting Rust to Gentoo, but I'd like to hear what OSes > and Architectures you use personally and professionally and why adding > Rust would be a bad idea. Is it corporate policy? Is it that the Rust > toolchain doesn't exist for your os/arch? Is it that Rust is a new > language and isn't as battle tested as C? Something else? > > I believe that even "I don't know Rust and don't want to learn it." > would be a valid comment to add as well. I think the discussion of > Rust has been so hot because we (the Git community) don't understand > everyone's situations and how they'll be affected, and what could > possibly be done to address concerns. Based on the domain of their email they use MacOS PowerPC. AFAIK LLVM has not supported it for a long time. Collin