@get @amiloradovsky @newt he was asked about rust in the kernel after one of the primary rust developers left because he felt mistreated and linus said something like "the debate is interesting" and talked for a few minutes about it without saying anything, and completely avoiding addressing that a dev left on bad terms over "the debate". He's normally very open with what he feels about things and I doubt he doesn't care at all so he must be treading lightly. If so, what or who is he afraid of offending.

the issue seems to be that to interface C and Rust you have to have a specification of what the C function does and the C developers in the Linux kernel considered documenting their internal functions to be onerous because they are always in flux. so it was a constant back and forth of demanding documentation, being told to fuck off, studying the code to figure out what some function was to get it working with Rust, then sometimes the function changing.

from the outside I look at this and I think that Rust should never have been allowed in the kernel. Not because it's bad but because there is an irreconcilable difference in how rust development and linux kernel development works.