>It's such a good tool I hear they are trying to write drivers with it in the Linux kernel.
And it's going to be a nightmare, because Linux famously makes changes every now and again which require maintainers monkeying all over code they do not know well to change references to functions and structures.
This is hard enough with just C, it is untenable with Rust.
Let's be honest. Linux isn't even that good. Is it worth the pain? The rust devs could get much more work done and without conflict if they worked on their own system, such as Maestro[0] (unix-like, AGPL but MIT if you go back just a few non-code commits) or Redox[1] (microkernel and multiserver proper, MIT).
And it's going to be a nightmare, because Linux famously makes changes every now and again which require maintainers monkeying all over code they do not know well to change references to functions and structures.
This is hard enough with just C, it is untenable with Rust.
Let's be honest. Linux isn't even that good. Is it worth the pain? The rust devs could get much more work done and without conflict if they worked on their own system, such as Maestro[0] (unix-like, AGPL but MIT if you go back just a few non-code commits) or Redox[1] (microkernel and multiserver proper, MIT).
0. https://github.com/maestro-os/maestro
1. https://www.redox-os.org/