| > Already done before in the second link here[1] "Already done"? Are you suggesting we should have been searching through your past HN comments for anti-Rust content? Your prior comment notes two issues re: Rust: 1. "A core problem with Rust is the lack of an adequate standard library." and 2. "The problem with Cargo is when you have an application with hundreds of dependencies." I'd say -- I'm not sure either is a problem in the kernel/the true object of this discussion. Re:1, as you may know, the Rust standard library isn't used re: the kernel. The kernel has its own Rust library, just like C has its own Rust library, klibc. C also has a much smaller standard library than Rust. C has nothing like Rust's collections or C++'s containers. Re: 2, I'm pretty sure the Rust for Linux team doesn't use Cargo for kernel code. The team simply vendors is deps. The video to which you linked is a reaction video of René Rebe to an article re: Rust. Let's be very clear -- Rene's issue had nothing to do with kernel space programming. Rene discussed Cargo in the context of the userspace tools for bcachefs, and why he doesn't particularly like what he sees as Rust's culture of micro dependencies. He also doesn't like Cargo as a build system, which auto-downloads deps from the cloud. Which is fair enough, but I think we can agree this is not really an issue re: Rust in the Linux kernel. I would further argue that composition is a feature of Rust. To put it mildly, C is not known for being easily composed. In C, you often just write something yourself, because C doesn't compose well with your app. > ... and then the developer sharing this content was the victim of an attempted SWAT What exactly are you suggesting? That, because you shared this content 25 days ago, that was the reason Rene was SWAT-ed? |