3 ms·
68MB seems excessive. Is that embedding an entire browser engine? (I see it's a Mozilla repo, and importing "TabsEngine"). 1-5MB is more typical, and while it's
by nicoburns 6y ago
68MB seems excessive. Is that embedding an entire browser engine? (I see it's a Mozilla repo, and importing "TabsEngine"). 1-5MB is more typical, and while it's certainly larger than C binaries, I don't think it's problematic for CLI tools. Unlike Java you still get instant startup.
Ripgrep is one of the most popular Rust CLI tools. It has ~2MB binaries: https://github.com/BurntSushi/ripgrep/releases https://github.com/BurntSushi/ripgrep/releases (except the windows GNU variant which is 8MB for some reason, but a ~2MB windows MSVC variant is available).
That's certainly a lot bigger than the ~50kb for my system's copy of grep. But it's also faster than grep for most use cases (see: https://blog.burntsushi.net/ripgrep/ https://blog.burntsushi.net/ripgrep/), and has better support for things like unicode. Seems like a pretty good trade-off to me.
- dathinab 6y agoIt's over 50MB debug info (see other comments). Release just specified the profile and you can override settings if it in Cargo.toml, e.g. to include debug info into release builds it disable lto. (Edit) which is done by the linked tool.