I started learning Rust because I wanted to get closer to the mechanics that application frameworks usually hide. The language makes memory, ownership, and concurrency part of everyday design rather than background concerns.
Useful friction
Rust’s compiler asks for clarity early. That can slow down the first version, but the questions are valuable: who owns this value, how long should it live, and which invalid states can the type system prevent?
My goal is not to replace every TypeScript service with Rust. It is to develop better systems intuition and use the language where predictable performance and strong correctness guarantees justify the tradeoff.