cross-posted from: https://sh.itjust.works/post/5850736
This is the resource I’ve been looking for. I’m working my way through the book but it gets in the weeds really early. It’s all fun and games and then chapter 4 just hits like a brick wall. Amos does a tremendous job explaining the why behind things, in a more wheels to the pavement way.
Yes, not to knock the book because it is really well done, but it gets theory deep before you’re able to apply that theory in a way that makes it make sense. It’s like someone describing the theory of gravity to you to teach you how to play basketball
Yea I can imagine.
I’m a pretty big believer in understanding the problem that needs solving before understanding the solution. I’d imagine that gets a bit tricky with rust because the compiler is just not gonna let you run the “problematic” program.
Now that I’m thinking this out loud … maybe a good way to learn rust would be by using and contrasting it with another language to see what rust is giving you that the other language doesn’t. Most are probably coming to rust from knowing a few languages already too.
To be fair, Rust is far from the hardest language I’ve learned. That honor would go to C++. I’m actually really enjoying it. But I’d maybe compare to learning english. You can learn all the funky grammar rules, the funky spelling, the history that went behind all that funkiness. But it’s filled with so many idioms that are just kinda baked in and not written down that it can get confusing fairly easily.