Only looked at the Cargo.toml files.
Cargo.lock files, and using = dependency versions for Phoenix_Desktop, is a bit odd!
People stopped taking Brian seriously when he helped create Go. That was pre-Rust.
Even the “talking points” here seem to be re-used from “Go vs. X” ones. Also, his experience speaks of someone who only tried Rust pre-v1.0.
Anyone who actually knows Rust, anti- or pro-, knows that what he said (partially in jest) is factually wrong.
Feel free to prove otherwise, especially the part about the performance of Rust programs. Don’t be surprised if he simply didn’t pass --release to cargo build, a common pitfall for someone in the “hello world” stage of trying Rust.
And this is why appeal to authority was never more fallacious, considering we live in a world where Dunning-Kruger is a universal reality.
What’s wrong with it
reqwest, which is what I expected you to immediately notice after I brought it into attention. You can obviously just remove it and use reqwest directly.reqwest with something malicious, or bad in some other way, in a v0.1.1 release. That (theoretical) release will be picked up after a cargo update call, or when Cargo.lock is not checked, which is the case by default with libraries.How did you find that crate?
Why do you think you need it?
Can you explain the rust-fetch dependency?
Why Peter Thiel though?
It was a (failed) joke about your user-name.
How much “vibe coding” is involved?
And are you Peter Thiel by any chance 😉
Or to avoid ad hominem accusations:
No code. Don’t Care.
And no benchmarks either. That intro about stack vs. heap also reads like someone who never went further than sophomore-level knowledge, or someone explaining things to kids.