>That said, the borrowing/ownership semantics of rust (at the time I looked at it) felt needlessly over complicated. Isn't it just “one mutator at a time”? >I

>That said, the borrowing/ownership semantics of rust (at the time I looked at it) felt needlessly over complicated. Isn't it just “one mutator at a time”? >Is there a K&R equivalent that an experienced programmer can get pick up to get productive with the language soon? (Opinion incoming.) The Rust Book[1] is great iff you are a complete beginner. If you are an experienced programmer, who knows his way around concepts like resource management and ownership, it's kind of a drag. Rust by Example[2] is much better. The Nomicon[3] is interesting, but it's mostly about unsafe. [1] https://doc.rust-lang.org/book/ https://doc.rust-lang.org/book/ [2] https://doc.rust-lang.org/stable/rust-by-example/ https://doc.rust-lang.org/stable/rust-by-example/ [3] https://doc.rust-lang.org/nomicon/index.html https://doc.rust-lang.org/nomicon/index.html