Rust Survey 2019 Results
Last year Rust was a language I badly wanted to learn. I&#x27;ve had many false starts learning a lower level or &quot;systems&quot; language, which I felt would round off my toolbelt quite well. A lot of principles of CS you don&#x27;t get exposed to when writing web servers and UIs.<p>The problem I had was basically the IDE integration in VSCode.  RLS was okay but unreliable. And if it only works most of the time, it may as well not work at all. Especially when it only sometimes gave me code completion and type checking (A lot of &quot;unknown&quot; would fill my code).<p>Then Steve pointed out Rust Analyzer in a previous thread and I was off to the races. Rust Analyzer has gotten _so good_. Having a VSCode setup that gives me immediate feedback for my mistakes and code discovery makes a huge difference (to me at least).  Maybe a bit of feedback is that I wish Rust Analyzer hadn&#x27;t been so hard to discover. Though maybe that&#x27;s just because it was new.<p>That, combined with my nightly march through The Rust Book has me well beyond, &quot;I wish I could learn a systems language but !@#$ C and C++ are just so complicated and unforgiving&quot; and into &quot;wow, it&#x27;s no-longer a matter of _if_ but a matter of how much I want to hone my understanding.&quot;  Rust is a beautiful language that way. It guides me away from rookie mistakes that would leave me disenchanted after hours of debugging something dumb. (It&#x27;s hard to be unrelentingly dedicated to learning something new now that I have young kids. When I was a teen it was easy)<p>I don&#x27;t want to come off as a Rust fanboy. I have yet to implement much of anything (though hopefully by next year I&#x27;ll have a Game Boy emulator to show you all).  But I want to give thanks and proselytize a little because it has been such an empowering experience.