Carefully exploring Rust as a Python developer
I'm thinking it's best not to make Rust a low-entry-barrier resume keyword.Rust is hard, and people should realize it's hard.One of the problems with C is that it was way harder than most people realized (we just accepted crashes, and then rampant security vulnerabilities, as normal), and so few practitioners got sufficiently competent at it.One of the problems with Python is that you don't have to understand much, to install a bunch of libraries and copy&paste snippets found in Web searches, to call something done.Rust will help you with analogs of some of the conventions that a very skilled C programmer might use.  But if someone only wants to get a well-paying job and be able to call their sprint tasks done, they probably want Python or Go, because Rust will make them cry.If I Web search for a Rust thing, I want to be finding genuine hardcore people talking.  (This was actually one of the biggest benefits of working in Scheme and Racket -- very high signal:noise ratio, because the practitioners were generally only there because they were very serious and/or very curious.  I'm moving to Rust, and hope to find similar.)