magic-wormhole.rs
min-sized-rust
| magic-wormhole.rs | min-sized-rust | |
|---|---|---|
| 5 | 101 | |
| 613 | 7,448 | |
| 3.8% | - | |
| 7.1 | 6.2 | |
| 5 days ago | about 2 months ago | |
| Rust | Rust | |
| European Union Public License 1.2 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
magic-wormhole.rs
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
> Downloading 3GB of dependencies is not a thing that happens in the Rust ecosystem. Reality is orders of magnitude smaller than that.
Assuming they're talking about the built size of dependencies that are left lying around after cargo builds a binary, they're really not exaggerating by much. I have no difficulty of believing that there are Rust projects that leave 3GB+ of dependency bloat on your file system after you build them.
To take the last Rust project I built, magic-wormhole.rs [1], the source code I downloaded from Github was 1.6 MB. After running `cargo build --release`, the build directory is now 618 MB and there's another 179 MB in ~/.cargo, for a total of 800 MB used.
All this to build a little command line program that sends and receives files over the network over a simple protocol (build size 14 MB). God forbid I build something actually complicated written in Rust, like a text editor.
[1] https://github.com/magic-wormhole/magic-wormhole.rs
- Efficient way of sharing files with someone without having to push
-
qft: A tool to quickly transfer files over a holepunched P2P connection
This is cool but it really should be using TCP. (You can do holepunching with TCP, check out https://github.com/magic-wormhole/magic-wormhole.rs/blob/master/src/transit.rs)
-
What’s everyone working on this week (8/2021)?
I'm contributing for some magic-wormhole issues, the book of rust-clippy , and exercism rust track ... Thank Almighty Allah.
-
What's everyone working on this week (7/2021)?
I'm working on some issues in magic-wormhole.rs and still looking around for other projects.
min-sized-rust
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust
This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...
The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?
-
Rust wont save us, but its ideas will
Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906
See also https://github.com/johnthagen/min-sized-rust
-
Making Rust binaries smaller by default
Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30
Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?
-
Was Rust Worth It?
Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.
-
Compiling Rust binaries for Windows 98 SE and more: a journey
A useful reference: https://github.com/johnthagen/min-sized-rust
- How to minimize Rust binary size
- Error on flashing embedded code to stm32f103
-
Tiny Binaries (2021)
That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...
-
Shared libraries
This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust
What are some alternatives?
denv - Dotenv (.env) loader written in rust 🦀
smartstring - Compact inlined strings for Rust.
CalcuLaTeX - A pretty printing calculator language with support for units. Makes calculations easier and more presentable with real time LaTeX output, along with support for units, variables, and mathematical functions.
Cargo - The Rust package manager
gbench
rustc_codegen_gcc - libgccjit AOT codegen for rustc
qft - Quick Peer-To-Peer UDP file transfer
c2rust - Migrate C code to Rust
math_lang - in progress pretty printing calculator language [Moved to: https://github.com/mkhan45/CalcuLaTeX]
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
syncbuf - A small library of append-only, thread-safe, lock-free data structures.
embedded-graphics - A no_std graphics library for embedded applications