I don't think you understand the scope of what you're talking about. Linux is tens of millions of lines of code, most of which is drivers that have to be written by vendors.
Vendors aren't going to write drivers for your hobby kernel. No one is using your hobby kernel. Bootstrapping a new kernel without billions of dollars to invest in development time is almost impossible, and anyone who is investing billions of dollars is likely going to have dubious proprietary reasons for doing so.
A successful kernel is Rust is probably the worst thing that could happen to the open source community.
>I don't think you understand the scope of what you're talking about. Linux is tens of millions of lines of code, most of which is drivers that have to be written by vendors.
But if you are Google and you believe that this Rust kernel is super safe and fast and has clean code, and parallelism,async and candy ... how many drivers do google Data centers use ?
After you prove the kernel is real good by using it in data centers and devices that need security you can slowly expand, for most devices you could create soem compatibility layer. Who knows if there are soem competent developeres hired to work on it they might use some better architecture, like keep the drivers outside the kernel.
Not very easily: Linux quite deliberately does not have any stable internal driver interface, so any such compatibility layer would have a very fast moving target to keep up with.
Vendors aren't going to write drivers for your hobby kernel. No one is using your hobby kernel. Bootstrapping a new kernel without billions of dollars to invest in development time is almost impossible, and anyone who is investing billions of dollars is likely going to have dubious proprietary reasons for doing so.
A successful kernel is Rust is probably the worst thing that could happen to the open source community.