382

'Maybe the problem is you' ... Linus Torvalds wades into Linux kernel Rust driver drama (www.theregister.com)

submitted 4 months ago by ray@lemmy.ml to c/opensource@lemmy.ml

142 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] conditional_soup@lemm.ee 54 points 4 months ago

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.

[-] catloaf@lemm.ee 19 points 4 months ago

It sounds like he tried that, and nobody with authority responded until he went outside the list. Even now, Linus hasn't actually answered the question of whether more rust code should be allowed.

[-] h4x0r@lemmy.dbzer0.com 4 points 4 months ago

No offense, but reading through the comments it's apparent you're not very familiar with systems programming nor linux development. This is a common problem with vocal 'rustaceans', rust is their hammer regardless of the domain.

Although considering rust is prudent, there are still a ton of advantages to using C for systems programming. It is not a binary choice, there are pros and cons, and every project should choose what aligns with their priorities.

No one has ever stated that linux will be in the kernel. It was 'go ahead and give it a shot', which includes convincing maintainers to accept your patches. Linus has delegated trust to subsystems maintainers and an established process.

Hellwig could have been more tactful, but like it or not, arguments against a cross-language codebase have merit. Framing it as a 'clear confession of sabotage of the r4l project', attempting to weaponize the CoC, and trying to drum up an army via social media was all out of line.

Success was never a given, if they want r4l to succeed then they have to get patches approved and crying wolf ain't gonna cut it.

[-] aspensmonster@lemmygrad.ml 10 points 4 months ago

Hellwig could have been more tactful, but like it or not, arguments against a cross-language codebase have merit. Framing it as a ‘clear confession of sabotage of the r4l project’, attempting to weaponize the CoC, and trying to drum up an army via social media was all out of line.

When a maintainer calls somebody's efforts "cancer" -- "spreading this cancer to core subsystems" -- and that they'll do everything they can to halt those efforts -- "I will do everything I can do to stop this" -- that's as clear an indication of sabotage as you will ever get.