Every week or so there seems to be drama about some old dude shouting about how rust in the Linux kernel is bad. Given all the open hostility, is there easier way for R4L to continue their work?
Every week or so there seems to be drama about some old dude shouting about how rust in the Linux kernel is bad. Given all the open hostility, is there easier way for R4L to continue their work?
I don’t understand why the R4L are even trying to get it into THE kernel at this point. Especially after the open hostility, but also after basically offering to be “downstream” of whatever C people do.
The difference to forking and gradually transitioning things to Rust seem technically minimally negative and socially enormously positive to me.
And when and if people want to use the linux kernel with Rust, made by the R4L people, they would then be able to do that? Idk.
I have no stakes in either side, so I don’t really care.
I think the issue with that would be increasingly working catch-up on newer developments of replaced functionalities.
If your end-goal is integration then it’s better to integrate early rather than late.
Developing and maintaining an interface and abstraction and having to keep that up to date is one thing. But after replacing some modules and components, any developments on their originals raises the question of how does that apply to our Rust module? If it already were in the Kernel and had replaced that module or component, that effort would not arise.