December 27, 2025
Borrow checker vs Ego: FIGHT!
Rust the Process
From rockets to ‘rusty balls’: learning by doing while comments brawl over clarity and missing tools
TLDR: A developer finally broke through Rust by building a raytracer and a terminal firewall UI, then shared the pain and joy. Comments split between praising the humble, hands-on approach and criticizing Rust’s opacity and missing tools like code coverage—proof the language is powerful but still maturing.
Popcorn time in Rust-land: a SpaceX alum finally “trusts the process” by ditching book-only study, building a flashy raytracer (cue the “rusty balls”) and a terminal firewall UI. The crowd isn’t just cheering—they’re split between vibes and vitriol. One camp loves the grit: the author fought Rust’s borrow checker (think: a safety referee that slaps your hand when you try risky moves) and came out wiser. Another camp grumbles that Rust “hides where stuff lives,” unlike old-school C/C++ where you know exactly where your data sleeps at night.
Tooling drama lit up the thread: folks begged for simple, built-in code coverage (a meter that shows how much of your code your tests actually touch), with one linking a design debate in Cargo, Rust’s build tool, here. “Make it easy!” they cry, while veterans shrug that this ecosystem still has growing pains. Meanwhile, meme energy spiked around “language holy wars”—the author joked about popcorn-worthy battles at SpaceX, and commenters kept that energy.
Best line of the day? “Fortunately, I’m not that smart.” The humility had Reddit swooning, even as others dropped hot takes that Rust’s memory rules feel opaque, just like Go. Rustaceans rallied: keep coding, not just reading, and let the dopamine from instant visuals do the teaching.
Key Points
- •The author previously relied on C/C++ in college and at SpaceX, where Rust and Go saw limited mainstream adoption in certain groups.
- •Shifting from reading to hands-on practice enabled progress in learning Rust.
- •The author completed a Rust implementation of “Ray Tracing in One Weekend,” leveraging a Rust-specific translation for rapid visual feedback.
- •To improve OpenSnitch usability on Linux, the author began building a Rust-based TUI using its gRPC API.
- •Development involved working with tokio and tonic, and encountering challenges such as Rust’s borrow checker and HTTP library quirks.