Re: And when we get shit code in Rust ?
We've spent 40 years learning that there are classes of mistakes that people make over and over again not because they're shit coders but because they're people.
Rust makes you do a bit of extra work up-front so the compiler can prove mathematically that you haven't made certain classes of mistakes.
Of course there is still opportunity for shit-ness but it'll be the same kind of logic bugs or bad design you can get in any language. At least there won't be dangling pointers, buffer-overruns and memory leaks too.