I'm not a Kernel developer, one day I might be (not smart enough yet), What I can do is express my opinions, concerns and thoughts about the future of the project, tho those who actually codes it, should be the ones to decide it.
Disclaimer: I love Rust so take my point of view with gigantic salty.
Somebody told them to get an abortion, and they just did. But I know better, I know what's best for them, and I know and I should decide what they should be doing with their body. They should not be getting abortions, nobody should, and I am sad and disappointed that this is happening.
Does this ring a bell?
Replace abortion with Rust, or a spoken language, or ...
… , my function body, …
Anything more specific than would probably de-anonymize me.
You know it's his kernel, right?
The OP claims that this somehow happened for Rust. People from the outside managed to somehow "push" us to use Rust in the kernel against our will, they dropped an email and we somehow were fooled by this people and started doing it. The OP is "sad"/"disappointed" that this happened.
If the OP were a kernel developer, (1) it would be accusing itself of getting fooled (yet their comment does not seem to realize this), and (2) it would know that this is not how the Linux kernel community works.
As a Linux kernel developer, I feel like non-kernel developers like yourself telling me which language I should use is definetly overstepping a boundary.
I couldn't care less about what non-kernel-developers think about this issue, but "since you mention this": please do mind your own business.
> Why, if C is so bad, wasnt one of the alternatives introduced to slowly replace C in the kernel years ago?
Because we, as in the actual people that spend their whole day developing the Linux kernel *do not want* to write and maintain Linux kernel code written in these languages.
> The only reason there is a push for Rust so much harder than anything else can only be explained by the community and their almost aggressive spirit of "if its not written in Rust, it should be".
This is so wrong. We, Linux kernel developers, are already writing drivers and kernel modules in Rust, *because we want to*. We now want to merge this new code so that other devs and users can use it. Most other devs want this too, so now we added Rust support to the Linux tree.
---
It really is that simple. My code, my body, my rules.
I really don't know what's so hard for people to understand here.