- cross-posted to:
- linux@programming.dev
- linux@sh.itjust.works
- linux@lemmy.ml
- cross-posted to:
- linux@programming.dev
- linux@sh.itjust.works
- linux@lemmy.ml
Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project:
https://lwn.net/ml/all/20250131075751.GA16720@lst.de/
The good news is this doesn’t affect drm/asahi, our GPU driver. The bad news is it does affect all the other drivers we’re (re)writing in Rust, two so far with a third one coming.
Another choice quote, calling R4L “cancer”: https://lore.kernel.org/lkml/20250128092334.GA28548@lst.de/
Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people’s energy and will to continue the project until Linus says “fuck you” or something.
As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch (which does not touch code formally maintained by the dissenter). Either Linus takes the pull, and whatever Christoph says is irrelevant, or he doesn’t, and R4L dies. Everything else is a waste of everyone’s time and energy.
Edit: Sent in my 2 cents: https://lore.kernel.org/rust-for-linux/2b9b75d1-eb8e-494a-b05f-59f75c92e6ae@marcan.st/T/#m1944b6d485070970e359bbc7baa71b04c86a30af
You must log in or register to comment.
I understand you’re emotional and frustrated (as are other parties), but your framing here is disingenuous. No one is ‘openly admitting to attempting to sabotage the entire Rust for Linux project’. You are encountering one of the known challenges of the project, and arguments against a cross-language codebase have merit. Existing maintainers have every right to push back where they see fit, as you have every right to advocate.
I’d be more sympathetic, but attempting to weaponize the CoC here really reflects poorly on you. You should focus on solving the problem, you might not succeed, but trying to drum up an army rather than doing the work casts you unfavorably IMO.
I broadly agree.
However, “Existing maintainers have every right to push back where they see fit” is tenuous when the Linux project as a whole has already (exhaustively) discussed and debated this exact question alongside all the other questions about adding Rust, and the explicit declared direction is that Rust should become an increasingly large part of the Linux kernel.
the explicit declared direction is that Rust should become an increasingly large part of the Linux kernel.
Who explicitly declared this? Where?
Switching to a more modern topic, the introduction of the Rust language into Linux, Torvalds is disappointed that its adoption isn’t going faster. “I was expecting updates to be faster, but part of the problem is that old-time kernel developers are used to C and don’t know Rust. They’re not exactly excited about having to learn a new language that is, in some respects, very different. So there’s been some pushback on Rust.”
I have seen that interview. Neither the excerpt you quoted nor the rest of the interview is what Thinker@lemmy.world claimed.
Let me guess, you get your Linux kernel development news from youtube?
Well said.
Agreed.
To be fair, though, OP’s username does say that he is a twelve-year-old. :)
The OP is not marcan, at least as far as I know.
Childish behavior all around, by the looks of it.
You can tell which engineers don’t work face to face in an office with a team of other engineers, because they end up sounding like this in text.
I never get involved in drama
After reading the lkml, it really does seem like the C dev just being hostile to Rust. The C dev just outright refuses to accept any of the compromises from the Rust dev, and is pretty rude about it.
Idk why, but some of these people need to hear that languages are not a team sport and fighting and being hostile to people about it just makes the Linux kernel worse.
