Rust is a practical solution to concrete problems that have hindered progress in software development for the last two decades. It is a leap forward in potential performance, scalability and productivity.
At a glance Rust looks like a C++ cousin, but it really is not, and the resemblance might actually prove misleading for newcomers. This has nothing to do with ability or experience – you just need to put in the time to acquire
So, here are a few suggestion on how to approach the language to ensure you have a greatest grasp in minimal time:
Step 1) First one is obvious: read
Step 2) Read RUST BY EXAMPLE, available at doc.rust-lang.org/rust-by-exampl… This is a great series of code snippets illustrating
Step 3) Read PROGRAMMING RUST, available printed or ebook at amazon.com/Programming-Ru… This is a fantastic book and the perfect finishing
Step 4) This is where you start writing your own code. A few more bits of advice:
- USE as basic a starting point as you can. The easiest way I’ve found is to use the crate “piston_window” the get a window
- LEARN and use the Rust standard library. It is great and very
- AVOID binding to/integrating any existing non-Rust code, yours or otherwise. Your current code base will be useful eventually, but for now do everything from scratch and limit yourself to the Rust ecosystem. It’s probably better than anything else you’ve ever
- TRY to write Rust code as idiomatic as you can. This is important in any language, but it is IMPERATIVE in Rust, where the language itself goes to great lengths and provides sophisticated tools to make sharing and integrating code with others as effective and
- Try to STOP thinking in terms of the patterns you are used to – do not try to replicate object oriented idioms with Rust. None of these abstractions are necessary or especially beneficial, and while they
- DON’T WORRY about debuggers or IDEs or
And finally: give it time. It will take a while, but you will find that Rust was well worth the investment.