Skip to main content


#Rust for #Linux #maintainer steps down in #frustration with 'nontechnical #nonsense'


source: https://www.theregister.com/2024/09/02/rust_for_linux_maintainer_steps_down/

The video depicts resistance to #Filho's request to get information to statically encode file system interface semantics in Rust bindings, as a way to reduce errors. Ts'o's objection is that C code will continue to evolve, and those changes may break the Rust bindings – and he doesn't want the responsibility of fixing them if that happens.


#C #Programming #nerd #kernel #problem #support #future #news #code

in reply to anonymiss

Seems like systemd has way more area/exposure to threats than the kernel.
in reply to anonymiss

This article does not mention systemd.
in reply to anonymiss

No I wrote OS. Systemd and everything else is OS. Kernel is kernel.
in reply to anonymiss

While systemd might aspire to being a kernel, it isn't a kernel, so I'm not surprised it wasn't mentioned.

But rewriting systemd in Rust would be a great idea! Convolution upon Convolution!

Stuffing Rust code into the monster of ever churning C code that is the Linux kernel is insanity defined, but as a firm proponent of BSD I can only say "push on!".

DeVault has already written (in just 27 days) a wee new demo kernel in his new Hare language and it is at least a million times more readable and elegant than even one small module of Rust code.

in reply to anonymiss

It does however mention a suggestion that the rust folks write a Linux compatible kernel. To which I suggest unless the Rust coders have an OS itch to scratch leave the kernel alone and work on younger systemd code with a greater surface area that would benefit from the things rust brings to the table.