I’m comfortable with C/++ and Java, to a greater extent than a lot of people I’ve worked with. There are still things in Rust that are papercuts: * The need to

I’m comfortable with C/++ and Java, to a greater extent than a lot of people I’ve worked with. There are still things in Rust that are papercuts: * The need to put :: before <> in expressions for generic parameters, but not in type signatures. * Using :: instead of just . even though most of the time the naming convention will delineate the difference anyway * Error handling with futures * Self-referential structs * Passing a shared pointer through multiple move closures IMHO the frustration involved in these things is not typically worth being more explicit. The :: thing may seem a bit pedantic, but it is simply more physical effort (Shift-colon-colon vs dot) and creates more visual noise. If/when all of the things above are addressed, I think Rust could give Python a run for its money.