"Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project". Thoughts on this post from Marcan?
"Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project". Thoughts on this post from Marcan?
Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project: https://lwn.net/ml/all/[email protected]/ 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...
Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project:
https://lwn.net/ml/all/[email protected]/
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/[email protected]/
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/[email protected]/T/#m1944b6d485070970e359bbc7baa71b04c86a30af
I get the feeling that it would be more feasible to build a separate kernel at this point. Its a lot of work, but adding another option to the comparatively small array of kernel options that we have might actually be a good idea -and in doing so, it word demonstrate r4l's willingness to maintain the project long-term. There's no need for this pissy behaviour, and there's no need to take the drama to social media.
Reading the whole thread seemed like a boomer crying that young people are ruin8ng stuff by adding new fangled stuff to their perfect utopian bloat.
Ok, this is made to sound worse than it is. You guys really huff too much drama.
„Why don’t you like that thing that I like!?”
Looks like Paolo served you a slice of humble pie there at the end.
Please keep this kind of FUD elsewhere, thank you.
Yeah...until Christoph replied and confirmed what Hector was saying was true and not FUD. He didn't mince words, he said he did not want Rust in Linux whatsoever, only for new codebases, not existing ones like Linux.
Christoph is an engineer and has been for a long time. There are probably considerations he is making that you either cannot or are refusing to fathom. He's clearly not against rust in general, just in mixing languages in one codebase.
To be clear though, I personally don't have a horse in this race, I am speaking somewhat as an outside observer, so i gain nothing from you getting your way or Christoph his.
Stop and think without attributing malice to why someone in his position would make the statements and decisions he's making. He's not an idiot.
I sincerely hope your reply in the mailing list was satire .
I can't wait for Brodie to report on this!
it's often the people saying "don't listen to all the drama" that are making drama.
chill out. the guy has relevant concerns, and they matter deeply to him. ..and they matter deeply to us, the users of Linux. Rust in the kernel is a good step forward, but processes need to be in place not just for code, but for people who will be dealing with a new language in their formerly-c-only environment.
win hearts and minds, don't just kick the nest and blame the hornets if they sting you. recognize needs, even of those who are stubborn, and address them.
