Re:Making Rust binaries smaller by default
by 0x000xca0xfe on Wednesday January 24, 2024 @08:16AM
(#39116899)
I'm not criticizing Rust, I'm criticizing statements that doubt whether the effort to reduce the binary size is worth it.
We currently have some nasty C++/boost monstrosities, if Rust can deliver a better development experience AND reliable stack traces AND smaller binaries, it would be HUGE for embedded.
Re:Making Rust binaries smaller by default
by pdimitar on Wednesday January 24, 2024 @08:45AM
(#39117257)
Stripping debug stuff has always been possible, yes, but that doesn't entirely address the problem of the stdlib being included piecemeal. I want a compiler who throws away everything that's not used in the final binary.
If that means that 90% of the stdlib is unused (which is likely true for many small projects) then it should not be included in the binary.
Re:Making Rust binaries smaller by default
by stefs on Wednesday January 24, 2024 @09:17AM
(#39117580)
Isn't that the linkers job? To throw away unused functions?
I remember this being the standard decades ago. It might not make sense in certain situations (i.e. with reflection), but that shouldn't be the default case anyway. What happened?
It's also important to remember that in embedded software, you're probably working in a no_std environment anyway, which means that the Rust standard library doesn't need to be included in the binary, which will already significantly reduce the size of your binary.
A lot of this is about tradeoffs, and I think the article does a good job of explaining what tradeoffs are relevant here. Yes, binaries should be as small as possible, but shipping multiple compiled standard libraries is also not ideal. The Rust team seem to have gone for a good default for people who are beginning, with lots of ways to tailor the build process for people who don't need debugging information, or who are willing to accept longer install/compile times in exchange for smaller, more optimised binaries.