After five years of daily Rust development, the author outlines persistent challenges such as long compile times, restrictive borrow‑checking, cumbersome async patterns, boilerplate from the orphan rule, and their impact on team productivity, while acknowledging Rust's safety and performance benefits.
After five years of using Rust for backend services, CLI tools, and embedded systems, the author outlines persistent frustrations such as long compile times in large workspaces, cumbersome borrow‑checker constraints, awkward async ergonomics, excessive boilerplate from the orphan rule, and the impact of these issues on team productivity, while acknowledging Rust’s safety and performance benefits.
The article, the second in the “From C++ to Rust” series, explains how Rust replaces C++’s return‑value and exception error handling with the Result type, the ? operator, and the thiserror/anyhow crates, and introduces Rust’s lifetime system, borrow checker, elision rules, variance, and common misconceptions for developers transitioning from C++.
