| > Is this mostly just a thing to get more young people interested in kernel development...allowing them to start out in less important areas and in a language they are passionate about? Not likely. At the moment you need to do extra work to get Rust working well. It's not exactly beginner friendly and doing work in the kernel, you'll need to dig into C anyway. > Or is this a serious proposal about the future of operating systems and other low level infrastructure code? Serious code already exists, so... Yes? > Do you just program everything in unsafe mode? What about runtimes? Why would you? You need that only when interfacing with something that can't hold the Rust compiler assumptions. See for example https://github.com/AsahiLinux/linux/blob/gpu/rebase-6.4/driv... The few places that need direct access / unsafe are almost all single-line areas with an explanation. > but it ain't the C culture if we are to accept that such a thing exists. I don't get that whole part of what you wrote. What seems to be the culture / why does it matter in the technical sense? Some parts of the compiler are written in C++ - what's the specific issue here? |