I don’t know anything about that project but it seems it is still written in C, which means it may just have the same issues with pushback if Rust was introduced.
The problem is about the Rust bindings from C code to Rust. I don’t understand what exactly went wrong there and why they are attacking each other. I think, it has something to do with C developer not caring about the Rust bindings and just breaking them as they wish. But I can be totally wrong here.
I think actually it might be a people problem. It shouldn’t be surprising that the people today that are still writing C rather than pushing for safe languages like Rust are quite hardcore about C and don’t give a damn about Rust. Any project still using C without any clear migration path will have such people I think.
Or work on GNU Hurd instead.
I don’t know anything about that project but it seems it is still written in C, which means it may just have the same issues with pushback if Rust was introduced.
The problem is about the Rust bindings from C code to Rust. I don’t understand what exactly went wrong there and why they are attacking each other. I think, it has something to do with C developer not caring about the Rust bindings and just breaking them as they wish. But I can be totally wrong here.
I think actually it might be a people problem. It shouldn’t be surprising that the people today that are still writing C rather than pushing for safe languages like Rust are quite hardcore about C and don’t give a damn about Rust. Any project still using C without any clear migration path will have such people I think.