Linux maintainers are unwilling to get rust into the kernel, so some rust folks decided to start writing a new kernel with same ABI. This allows them to make new architectural decisions. An example being their “frame kernel” (something between a monolithic kernel and a microkernel).
If I may say, it’s more legible and the tooling is way better, right off the bat.
All source code in Rust is statically-linked when compiled, which thereby renders the LGPL no different from the GPL in practice. For Rust, the MPL-2.0 is a better license because it does not have the linking restriction.
Interesting. Is that because the kernel can’t load a a module as dylib (I don’t know a lot about kernel development) or because dylibs are also somehow statically linked in Rust?
Huh, I didn’t know that. I thought dylibs could just be linked normally. Thanks for the insight.