This might make a much more interesting case for GOT than before https://www.gameoftrees.org/

GCC simply supports more platforms.

RESF members tend to say it the other way around as in the platform doesn't support rust, but the reality is that it's the compiler that needs to support a platform, not the other way around.

[1] https://doc.rust-lang.org/beta/rustc/platform-support.html

Ctrl+F for "NonStop" in https://lwn.net/Articles/998115/

> I like programming

> I program to make money

If you belong to the second category - I’m going to be super charitable, it sounds like I’m not going to be charitable and I am, so keep reading - such as by being paid by a giant bank to make applications on Nonstop, there might be some policy that’s like

“You have to vet all open source code that runs on the computer.”

So in order to have Rust, on Nonstop, to build git, which this guy likes, he’d need to port llvm, which isn’t impossible. What’s impossible is to get llvm code reviewed by legal, or whatever, which they’re not going to do, they’re going to say “No. No llvm. HP who makes Nonstop can do it, and it can be their legal problem.”

I’m not saying it’s impossible. The other guy is saying it’s impossible, and I’m trying to show how, in a Rube Goldberg way, it looks impossible to him.

You and I like programming, and I’m sure we’re both gainfully employed, though probably not making as much money at guy, but he doesn’t like programming. You are allowed to mock someone’s sincerity if they’re part of a system that’s sort of nakedly about making lots of money. But if you just like programming, you’d never work for a bank, it’s really fucking boring, so basically nobody who likes programming would ever say porting Rust or whatever is impossible. Do you see?

It’s tough because, the Jane Street people and the Two Sigma people, they’re literally kids, they’re nice people, and they haven’t been there for very long, they still like programming! They feel like they need to mook for the bank, when they could just say that living in New York and having cocktails every night is fun and sincere. So this forum has the same problem as the mailing list, where it sounds like it’s about one thing - being able to use fucking hashmaps in git - and it’s really about another - bankers. Everywhere they turn, the bankers run into people who make their lifestyle possible, whether it’s the git developers who volunteer their time or the parents of the baristas at the bars they’re going to paying the baristas’ rent - and the bankers keep hating on these people. And then they go and say, well everyone is the problem but me. They don’t get it yet.

Looking at the comment thread, at least one person I recognize as a core maintainer seems to be acting as if this is an official plan that they've already agreed on the outline of, if not the exact timing. And they seem to acknowledge that this breaks some of the more obscure platforms out there.

In a brief search, they’re engineering manager for GitLab, appear to be a frequent contributor of high-difficulty patches to Git in general, and are listed as a possible mentor for new contributors.

Given the recent summit, it seems likely that this plan was discussed there; I hadn’t dug into that possibility further but you could if desired.

But we probably won't see any effect for 10 years or so.

I need to to fill out this TPS report. Unfortunately it's mandatorty to fudge section 15A.

And they will keep working because the repository format isn't affected by the language git is written in.

You are. This is firm "I don't want to have to learn new things" territory, which isn't a viable attitude in this industry.

In any case Rust is usually easier than C (excluding buggy C which is very easy to write), and certainly easier than actually learning the Git or Linux codebases.

So "another language" here probably does not weigh as much, especially considering perl/TCL are the weirder one there.

But for big projects like linux and git, this could actually be a consolidation step: you spent decades growing, hacking things on top of each other.

You have mostly figured out what this project is and where it is going, it's time to think about safety, performance and remove old hacks.

Rust feels like a good fit, imho.