I am using Rust building a privacy focused in-app file system ZboxFS(https://github.com/zboxfs/zbox). The fun part is not only joyfulness Rust bring to me, but also learned a lot about cryptography, file system, transaction control and many more interesting areas.
At https://www.3dhubs.com we're using Rust to build the geometry processing side of our platform, which is the most computationally intensive custom part. Previously it was in C++ and we're a lot happier after migrating to Rust two years ago.
Still missing a reasonable GUI though.
What I really liked about Rust in this project is the peace of mind it gives about safety, the performance, async features and the powerful procedural macros.
Not different, if "safety" is your only criteria. GC languages provide memory safety at a cost (performance). C, C++ and Rust are preferred in settings where you don't want the GC to capriciously affect performance (e.g. HFT). However, out of the 3, Rust is the only one that is provably "memory safe" at compile time because it provides constructs (ownership, borrowing) that force you to write safe code. If your Rust code can compile it's more than likely safe.
You can write equally performant code in C / C++ but both languages have a lot of foot guns.
I'm working on a command line application which generates and executes randomized patch request against a rest API after looking at a JSON schema provided as input.
I have almost finished the harder parts of it, but I have not been able to work on the final part (the binary with command line flags and recording the patch responses) for a couple of months.
