Post AlkFhrUOUVgBTs9o8G by kazriko@alcatir.com
 (DIR) More posts by kazriko@alcatir.com
 (DIR) Post #Ald6Wx0VNNTbiOBD1c by pro@mu.zaitcev.nu
       2024-09-03T14:58:24.603450Z
       
       0 likes, 0 repeats
       
       It had this conversation on TwitX just recently.Zealot: Rust adds memory safety! Therefore we must use Rust in kernel!Zaitcev: But Rust is not the only compiled language that adds memory safety. What about D and Go?Zealot: screeeee! Python suuuucks!!!I understand that D and Go have some undesirable baggage. D is used widely by the BSD types, and Go is weirdly crusty for a language that young. But if memory safety is your overriding concern, why Rust and where have you been all this time?
       
 (DIR) Post #AlkFhrUOUVgBTs9o8G by kazriko@alcatir.com
       2024-09-07T01:36:09.879585Z
       
       0 likes, 0 repeats
       
       @pro I think someone did some testing with various languages, and the two that had the fastest results were C and Rust, with C++ coming in 33% slower than both of those in the tests they did, and Go being worse than C++, so it's more a combination of memory safety and not impacting speed significantly. As far as development, if you can figure out how to work with the borrow checker, then Rust code does make the development easier than C, and much closer to Python in capabilities.
       
 (DIR) Post #AlkFhsV8jDs0cTVuvw by pro@mu.zaitcev.nu
       2024-09-07T01:44:09.305781Z
       
       0 likes, 0 repeats
       
       @kazriko I see, thanks. Not sure how credible it was, but a data point anyway.
       
 (DIR) Post #AoZeAPUjnuXvqmymae by pancake@infosec.exchange
       2024-11-30T08:44:28Z
       
       1 likes, 1 repeats
       
       @pro the main problem is the runtime. D and Go runtimes have garbage collection tightly tied to the language so can’t work on kernel. Thats why nobody can replace C yet. Swift embedded, Zig and Hare are the only real choices imho. But all of them are too young to be used in production. Not to mention C interop in Rust is awful
       
 (DIR) Post #AoZeJftOCvKHJSvZho by pro@mu.zaitcev.nu
       2024-11-30T16:34:26.540915Z
       
       0 likes, 0 repeats
       
       @pancake I'm educating myself on these issues. We have a large D project at work and it has nogc pragmas all over. Apparently a GC run involves a 200mS stop and we cannot afford that.