3 ms·
I did like to book. I read it in small steps over like 3 weeks. The only thing that's really missing and makes people get a rough start is, that there is no ste
by noxer 6y ago
I did like to book. I read it in small steps over like 3 weeks.
The only thing that's really missing and makes people get a rough start is, that there is no step-by-step dev environment setup. VS Code + Rust (apparently what most people use) should work "out of the box" but nowhere is an official and maintained recourse how to set it up correctly. Just a bunch of outdated blog posts how someone someday got it to work. If you never used VS Code before you are almost certainly waiting hours to get you rust scratchpad running which you definitely want to have while reading the book.
Yes, is may not really fit in the book but then there should be a official place for this. Preferably with different OSes and IDEs covered.
- satvikpendem 6y agoThe book should mention that one should use rust-analyzer rather than RLS as the code completion engine in VSCode. The former is much better.
- steveklabnik 6y agoThis is part of why doing this is tricky, and why we don't. If this section were in the book today, it would say the RLS, because the RLS is the current project from the Rust Project proper. That's about to change, but still, it's a good example of why this is hard.
- noxer 6y agoIt should ofc name both and give all the information needed for a beginner to make a educated decision what to use. But like I said the book may not be the right place for this but there MUST be a place for this and if not then such a place must be created. Many many other languages/frameworks etc. have the same problem.