<story><title>Rustaceans at the border</title><url>https://lwn.net/SubscriberLink/889924/2b330ed9ea4a9e23/</url></story><parent_chain></parent_chain><comment><author>geijoenr</author><text>I believe Rust will benefit from the reality check that kernel development represents.&lt;p&gt;Kernel development is hard, and bullshit doesn&amp;#x27;t go very far in that context. Success for Rust in that environment (with some changes along the way) will be a proof of value.</text></comment>
<story><title>Rustaceans at the border</title><url>https://lwn.net/SubscriberLink/889924/2b330ed9ea4a9e23/</url></story><parent_chain></parent_chain><comment><author>proto_lambda</author><text>I can sympathize with the need to have all required source code in the repository and not having to fetch a bunch of dependencies at build time. Thankfully, cargo already offers a solution here: `cargo vendor` will download all the specified dependencies once into a local directory, which can then be checked into the source tree.&lt;p&gt;This maintains cargo&amp;#x27;s dependency resolution&amp;#x2F;update checking&amp;#x2F;etc, but also allows for all dependency code to be kept alongside the kernel code and audited accordingly.</text></comment>