Comment by MyOutfitIsVague
10 months ago
The problem is that they might want their drivers to actually work on people's existing Linux systems without having to force them to use a forked kernel.
It's like telling people who want JPEGXL in Firefox to "just" fork the browser, ignoring the massive extra effort that you actually have to convince everybody to use your fork instead of the original.
What extra effort? If you match upstream it's a drop in replacement and anyone who cares will use it. If they don't it's because they don't care.
And what if they do care, but they simultaneously need features available in multiple different forks? You can't run two kernels at the same time.
Then it means the rust code does impact the C code and the rust people were lying.
2 replies →
"if you match upstream"
Talk about aggressively missing the point.
Explain what the point is.
Rust developers are promising that rust in the kernel should have no impact on c in the kernel.
If rust in the kernel has no impact in c then you should be able to remove the rust from the kernel and move it to it's own project, since it will have no impact on the c either way.
Linux is the most important open source project ever. The barrier to entry is, actually, shockingly low.