As a C programmer (and often assembly), I looked into Rust. I battled Javascript in 1999, and declared it my enemy. I tried to learn Perl, but it makes my brain hurt. I learned and used PHP OO to develop a useful web database project, and for certain jobs, I like it. I found some Python code behind a dumpster and tried to understand it, but I hated the way the types could just change without my consent. Getting the actual facts of an object was not easy. Maybe good Python code is wonderful, but the language seems to allow absolute crap.
Rust opened up a new OO that really made sense to me. I liked that the compiler refuses to allow certain bad or lazy practices. The ownership idea was new to me, but it makes sense. I went through all of the code in "The Book" and at the end I was impressed with all of the features of Rust.
I feel that Rust can be an effective barrier to keep the crappy coders away from critical systems. Those who cannot pass the compiler are just not qualified to write that code. Maybe they can find employment writing style sheets.
My current projects are embedded C, so I don't use Rust, but I appreciate the advancement that Rust gives to medium and large projects.
That said, I hope that Rust gets a final specification that firmly NAILS DOWN for good a standard that will not and can not change, so developers can be confident that they won't chase a moving target.