I wonder what approach acts as the best mentor for someone who wants to eventually develop a good mental model for how systems work. The C approach where you suffer at runtime and then have to debug ferociously, or the Rust approach where your mentor hits you with a stick all day?
I had C programming experience before touching Rust. I may be biased, but I think this is the right way to understand how computer systems work. Otherwise, Rust's design choices will make little sense to you.
Some observations:
- The compiler is always right.
- Do what clippy and rust-analyzer says. Don't ask questions.
- If you're fighting the compiler, clippy, AND rust-analyzer, then you're almost definitely wrong.
Virgins try to use &str everywhere. Chads just use String.