>The next article in this series will look at the design of the interface between the C and Rust code in the kernel, as well as the process of adding new bindings when necessary.

This is the actual useful one since so little of the kernel has Rust bindings. When I tried to implement a filesystem driver in rust I spent most of my time trying to write bindings instead of trying to write a filesystem.

I'm curious, who's driving the interest in Rust. Do people learn it in CS degree's and thats all they know? Do orgs like it as a language because its considered safer in the sense that there are usually less bugs compared to C++ (and hence get it introduced into CS degrees)? Is it that C++ has become an abomination over time with added features? Cant we just use C++ as C with polymorphism and encapsulation? Is it generics that are the sticking point (and people don't like STL)? Or is it simply that a new gen just want to have their own thing to differentiate themselves from the oldies... its more cool.

I personally invested a lot of time and effort into learning C/C++ and the only new language with enough difference to come along that was worth learning was Python imho. Not sure what significant differences Rust brings that warrant throwing all that knowledge away and starting again.