magic-wormhole.rs VS qft

> 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

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)

I'm contributing for some magic-wormhole issues, the book of rust-clippy , and exercism rust track ... Thank Almighty Allah.

I'm working on some issues in magic-wormhole.rs and still looking around for other projects.

And another similar one tool is QFT which is pure p2p (the only embedded STUN used to find peers)

qft

I would use something like qft or croc for file transfers on an internal network, and not have those machines connected to the Internet (or have file transfers use only an internal/private network adapter/IP).

croc or qft or SimpleXChat.

croc or qft.

The git repo: https://github.com/tudbut/qft - The releases page has precompiled binaries for linux, mac, and windows.