Sometimes I get the impression from rust advocate articles on HN that they are snobs. Not here; no way. This was well written, cheeky, thorough, and gave me a s

Sometimes I get the impression from rust advocate articles on HN that they are snobs. Not here; no way. This was well written, cheeky, thorough, and gave me a solid sneak peak at doing rust from a c/c++/go/python/Java background. The exacting standards of stopping data races at compile time is an exacting task. I think I followed most everything here, although I wondered if the crossbeam inclusion should be in language not library code ... But I don't know enough to press further. Solving problems in libraries not language probably is better. Rust is one of few if only languages I am aware of that hit hard on data safety without a gc. That'll make it quite different to the programmer.