how is that not the same thing?

wongarsu · 2025-09-20T14:03:43 1758377023

You could read "Rust will become mandatory" as "all contributors will need to be able to code Rust" or even "all new code has to be written in Rust" or similar variations

account42 · 2025-09-22T13:07:34 1758546454

It's still effectively the same thing. You don't take on a huge dependency like that without planning to use it extensively.

StopDisinfo910 · 2025-09-20T14:01:02 1758376862

One phrasing implies contributions will have to be in Rust, the other doesn’t.

I was confused in the same way after reading the submission title. Mandating Rust would be a far more radical change.

binary132 · 2025-09-20T14:02:57 1758376977

I see. No, I understood it the way it is, as introducing it as a new hard dependency in git 3. I suppose it is a pilot for making it mandatory for contributions / incrementally replacing the existing code in the future, though.

ekidd · 2025-09-20T14:24:10 1758378250

Git is pretty modular, and it already includes multiple languages. I guess that significant parts of it will remain in C for a long time, including incremental improvements to those parts. Though it wouldn't surprise me if some parts of git did become all-Rust over time.

kstrauser · 2025-09-20T14:13:55 1758377635

My last company used Jenkins, so our build infrastructure depended on Java. We used zero code outside of supporting Jenkins. So Java was required to build our stuff, but not to write or run it.

Edit: nope, I’m wrong. On reading the link, they’re setting up the build infrastructure to support Rust in the Git code itself.