Skip the Theory: Why Building Projects Now Beats Reading 'The Rust Book' for Beginners
The consensus screams that theory alone is a trap. The most effective path to learning Rust is hands-on coding, building concrete projects like CLI tools.
The primary fight centers on prerequisite knowledge. 'locuester' and 'Kissaki' forcefully argue against academic delays, stating, "it’s much more useful to just start USING and DOING." Meanwhile, some insist on deep background theory, pointing to OS concepts and memory allocation as necessary groundwork.
The weight of opinion demands action over absorption. While resources like Rustlings are suggested, the undeniable trend is toward immediate application—build something functional, rather than endlessly studying abstract concepts.
Key Points
Learning must be project-based.
The general consensus, backed by advice to build things like CLI tools (FizzyOrange) and the focus on practical application.
Delaying coding for deep theory is advised against.
'locuester' and 'Kissaki' argue vehemently that theory alone is insufficient, demanding users just start 'DOING'.
Standardizing String and Path handling is crucial.
'hades' and 'Kwdg' repeatedly advised using &str over &String for arguments and preferring slices &[T] over &Vec<T>.
Error handling must favor results over panics.
'hades' stressed that functions must refactor to return Result types instead of relying on `panic!()`.
Separating I/O from Parsing improves design.
'nous' offered specific structural advice, recommending separating the file opening responsibility from the parsing logic for better testability.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.