@Lyude @lina @desttinghim
>The reality is if someone like this doesn't see "the value" in rust then they should be required to find someone else who can be trusted as a maintainer to handle the code
Replacing maintainers that worked on a piece of code for years with someone else only because 'they don't see "the value" in rust" is insane.
>I don't know how folks like Linus actually expect rust to pick up in the kernel if we don't address the maintainers who clearly want nothing to do with this.
There are reasons why maintainers want nothing to do with Rust. Maybe, just maybe, improve Rust instead of complaining about Linux maintainers on social media, because in the end shouting into the void about it will improve absolutely nothing about the situation.
I'm calling it now, Rust in Linux will be gone in few years just like C++. The only reason why it hasn't been done yet is because more people are interested in Rust than in the hell called C++.
>The reality is if someone like this doesn't see "the value" in rust then they should be required to find someone else who can be trusted as a maintainer to handle the code
Replacing maintainers that worked on a piece of code for years with someone else only because 'they don't see "the value" in rust" is insane.
>I don't know how folks like Linus actually expect rust to pick up in the kernel if we don't address the maintainers who clearly want nothing to do with this.
There are reasons why maintainers want nothing to do with Rust. Maybe, just maybe, improve Rust instead of complaining about Linux maintainers on social media, because in the end shouting into the void about it will improve absolutely nothing about the situation.
I'm calling it now, Rust in Linux will be gone in few years just like C++. The only reason why it hasn't been done yet is because more people are interested in Rust than in the hell called C++.
Follow
@phnt
> Maybe, just maybe, improve Rust instead of complaining about Linux
Catering to the people never helps either, the problem described in the opening post isn't about Rust, it's about interfaces *already implemented in the kernel* — Linux maintainers are reluctant to change them, even if you offer them the option of changing the language to their needs, they will just keep making those up as an excuse to not use it, the problem isn't Rust 🤷
@desttinghim @Lyude @lina
> it's about interfaces *already implemented in the kernel* — Linux maintainers are reluctant to change them
Of course maintainers are reluctant to change them, when you are working with a piece code that is extremely fragile like drm, possibly one of the most fragile subsystems in the kernel. It regularly breaks every few months in stable releases when someone touches it.
You don't want to reengineer that whole thing. Fixing it would require cooperation with AMD, Intel and nVidia on a larger scale, which is a thing that won't probably happen.
Trying out Rust in drm/video drivers instead of more much simpler drivers was a bad idea.
>even if you offer them the option of changing the language to their needs, they will just keep making those up as an excuse to not use it, the problem isn't Rust
Then abandon it. It does not matter that Linus and other kernel maintainers want Rust, if the maintainers of the individual subsystems don't want it. You can't force them to use and maintain Rust. That's not how cooperation in large scale open-source projects work. Linux isn't a corporate project where things like this are normal. You can force them to resign in which case you will be likely in a state where no other maintainer wants to step up.
Rust is also the problem in this case as it is a rapidly changing language with a plethora of problems I won't repeat for the 5th time in this thread.