News for hackers. Stuff that matters.
Re:Embedded Rust or C Firmware? Lessons from an Industrial M... by cyberpunk on Sunday May 03, 2026 @02:57PM (#48000181)
shrug I guess we have different experiences. Any even small sized rust application I've come across rivals nodejs for amount of deps it pulls in.

Sure, just vendor them in, simples, right?

Re:Embedded Rust or C Firmware? Lessons from an Industrial M... by IshKebab on Sunday May 03, 2026 @04:11PM (#48000889)
You could do (it is simple), but all the code is stored on crates.io so there's no real need.

An exception is for crates that wrap C code which might get the code from elsewhere but those are quite rare.

Re:Embedded Rust or C Firmware? Lessons from an Industrial M... by cyberpunk on Sunday May 03, 2026 @04:41PM (#48001257)
And they’re immutable, forever? No one can pull a leftpad?
Re:Embedded Rust or C Firmware? Lessons from an Industrial M... by cdirkx on Sunday May 03, 2026 @05:08PM (#48001519)
Yes, they are immutable. It's only possible to "yank" a specific version, which will prevent new dependencies, but it will still be available for download for existing dependencies.

https://doc.rust-lang.org/cargo/commands/cargo-yank.html

Re:Embedded Rust or C Firmware? Lessons from an Industrial M... by dwattttt on Sunday May 03, 2026 @05:44PM (#48001864)
To elaborate on "prevent new dependencies", dependency resolution will never choose a yanked version. However the yanked version remains hosted.