110

One Of The Rust Linux Kernel Maintainers Steps Down - Cites "Nontechnical Nonsense" (www.phoronix.com)

submitted 2 months ago by shield_gengar@sh.itjust.works to c/rust@programming.dev

29 comments fedilink hide all child comments

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

[-] beepnoise@piefed.social 27 points 2 months ago* (last edited 2 months ago)

It's such a shame that Rust developers feel like they feel unwelcome, especially due to a complete misunderstanding in implementation details.

Even worrying, this is kernel developers saying they prioritise their own convenience over end user safety.

Google has been on a Rust adoption scheme, and it seems to have done wonders on Android: https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html?m=1

But also, there is a bit of a problem to adopt Rust. I think the memory model may prove challenging to some, but I do worry in this case that even if it was super simple, the existing C kernel devs would still reject the code due to it not being C and not willing to adopt a new language.

[-] HoloPengin@lemmy.world 11 points 2 months ago* (last edited 2 months ago)

There's a long thread on Mastodon by the main Arm Mac Graphics dev for Asahi Linux. Perhaps one of the fastest developed and most stable graphics drivers ever made, thanks to a couple amazing developers but also very very much thanks to Rust. And one of the kernel devs flippantly calls it an "unmerged toy project" as if it's not kernel devs' fault that useful stuff and even small non-breaking improvements to existing systems are so incredibly hard to get merged. Not to mention that writing the entire m1 graphics driver in Rust ended up actually thoroughly documenting the DRM subsystem's API for the first time as a side effect because everything the Rust code interacts with pretty much gets strictly defined within Rust's type systems and lifetimes.

https://vt.social/@lina/113056457969145576