My take
Why I use Rust
Rust earns its reputation. The borrow checker forces correctness up front, and the result is software that runs fast, fails predictably, and avoids whole classes of bugs. I reach for Rust when I need both speed and certainty.
Want the broader stack philosophy? Read about how Sri picks tools or browse engineering insights.
Honest assessment
Strengths & tradeoffs
No tool is perfect. Here's what shines and what to watch for.
Strengths
- Memory safety without garbage collection
- Best-in-class performance - competitive with C and C++
- Fearless concurrency thanks to ownership rules
- Excellent tooling: cargo, clippy, rustfmt
- Growing ecosystem in tooling, embedded, and WASM
Tradeoffs (honestly)
- Steep learning curve - borrow checker fights are real
- Compile times can be slow on large projects
- Smaller ecosystem than Go or Node for web work
- Higher cognitive overhead for typical CRUD apps
Fit assessment
When to reach for Rust
Pick the right tool for the job.
Best fits
Performance-critical libraries and engines
WebAssembly modules for the browser
Systems-level CLI tools
Embedded systems and firmware
Cryptography and security-sensitive code
Not ideal for
Rapid prototyping and quick iteration
Standard CRUD web apps where TS/Go suffice
Teams without time to invest in the learning curve
Common use cases
Resources
Learn more
Curated official docs, tutorials, and writing on Rust.
Services
Where I apply Rust
Engagements where this technology shows up regularly.
Case Studies
Rust in production
Real engagements where this technology shaped the outcome.
Browse the full case study archive.
Stack
Pairs well with Rust
Tools and platforms I commonly combine with this one.
Languages
More in this category
Languages I use as primary tools across the stack.
Need help with Rust?
Whether you're starting fresh or optimizing an existing implementation, I can help you get the most out of this technology. Read more in insights or get in touch.