I see your point, but in this case I feel OP was misinterpreting the situation
witx
joined 1 year ago
But that's the thing where you are wrong. They clearly state they don't want C developers to learn Rust. In the particular video posted he was saying "I want you to explain to me how this particular API works so that I can do it"
The concerns about who fixes what on a merge when the C code breaks Rust code are valid, but that's easily fixed by gathering with the Rust developers, explaining the changes and letting them fix it.
Sure and place neovim there
Can you point out where I said that?
The issue is not agreeing, but behaving like an immature prick when arguing
Is it a lie though?
Isn't Linux still Linux even though probably a lot of the original code is gone? Why would slowly rewriting it whole, or just parts, in Rust make it stop being Linux?
I agree with your views. But I have to give praise to Linus for bringing Rust into the kernel.
Yes I agree but the solution for a project so big and critical is not to fork. How do you maintain all of it while at the same time adding support to Rust?
The difference is that now you have a scope of where the memory unsafe code might be(unsafe keyword) and you look there instead of all the C code.
view more: next ›
I also never had an accident where I needed the seatbelt