https://lore.kernel.org/lkml/[email protected]/

Here’s the source thread.

Tldr: someone wants to put rust in the dma part of the kernel (the part that accesses memory directly)(it’s a memory allocator abstraction layer written in rust which rust code can use directly instead of dealing with the c allocator abstraction layer), is told that rust should use the extant methods to talk to the c dma interface, replies that doing so would make rust programs that talk to dma require some more code, gets told “that’s fine. We can’t do a split codebase”. The two parties work towards some resolution, then hector martin comes in and acts like jerk and gets told to fuck off by Linus.

Martin is no lennart poettering but I don’t try to see things from his perspective anymore.

It’s worth noting that Linus’ “approval” of rust in the kernel isn’t generally seen as a blanket endorsement, but a willingness to see how it might go and rust people have been generally trying to jam their code everywhere using methods that rival the cia simple field sabotage manual.

I don’t think it’s on purpose (except for maybe Martin) but a byproduct of the kernel maintainers moving slowly but surely and the rust developers moving much faster and some seeing the solution to that slow movement as jamming their foot in the door and wedging it open.

Shit they triggered the raid boss early

FTA: "However, I will say that the social media brigading just makes me not want to have anything at all to do with your approach.

"Because if we have issues in the kernel development model, then social media sure as hell isn't the solution. The same way it sure as hell wasn't the solution to politics.

"Technical patches and discussions matter. Social media brigading - no thank you." -Linus

Yeah, I have to issue an unqualified agreement here. Linus isn't saying no to Rust, he's smackin' that ass for bringing drama out into social media instead of working through it in normal technical discussion channels.

This whole thing reads not like a codebase versus, but a traditional engineering approach (don't act like you can patch this once you release it - get it done so it's stable the first time) versus the more modern "move fast and break things" approach.

I am so glad Linus just came out and said it. I was pretty upset at Hector too in the other thread the other day, and I especially didn't appreciate a call to remove a major developer from the kernel because Hector wasn't getting his way. Very militant action on Hector's part where it just wasn't necessary.

Hector, if you're reading this, communication skills are just as if not more important than your Rust development skills, and frankly your communication skills lack.

This is just a dick measuring contest.