Counterargument: Linux is almost 35 years old (wow, time flies). Rust for Linux is a project started at the moment of biggest rust hype. It's understandable that the Linux maintainers are wary of introducing too much rust dependence, in case, for example, all the rust people leave in 5 years and current/old maintainers are stuck with it forever
Counterargument Counterargument: one would think 35 years is enough to work out the memory safety kinks. If C people can't sort it, a new solution needs to be used.
Not necessarily Rust, but something memory safe. Perhaps Java (if maintenance is that important) :P
> the people actually working on it has opinions about the work they're doing
No. They have opinions and take actions to subvert related work. See people literally stopping a presentation to gripe about Rust cultists, or Hellwig throwing a hissy fit because he doesn't like that Rust code is adjacent to his DMA controller.
This isn't technical discussion, this is Office Politics 104.
Not wanting a mix of programming languages in a project is a fairly reasonable opinion for someone to have in many circumstances.
If rust is a really good fit for the kernel I imagine people will adapt over time... so far it doesn't seem promising. If the main fear is that you'll end up having to maintain a bunch of rust code, the propensity for the rust people to rage quit doesn't really allay that fear.
If no one wants to do the thing you think is obviously better, you might be a misunderstood genius, or you might be wrong.
> Not wanting a mix of programming languages in a project is a fairly reasonable opinion
That's a not what happened. Hellwig asked that Rust in Linux guys not write common bindings to his layer but do it per driver.
In other words he as DMA code maintainer gets to choose what and how other people use his interfaces for. That's not how interfaces (as in two environments in software interacting ) work.
By that logic if he hates Logitech drivers he can sabotage them because he doesn't like how the devices look?
> In other words he as DMA code maintainer gets to choose what and how other people use his interfaces for.
He as DMA code maintainer choose no Rust code. However he then can't choose to veto Rust code bindings. He could have choosen to have Rust code and that would have given him the veto.
