> “We have to make things easier without losing the advantages that Rust has for its core focus of systems programming. Reducing the need for explicit lifetimes

> “We have to make things easier without losing the advantages that Rust has for its core focus of systems programming. Reducing the need for explicit lifetimes, making the borrow checker more powerful, not overcomplicating the trait system, focusing on user experience, and avoiding becoming a huge language will all help.” I think that tooling helps with stuff like this. I can’t imagine writing Rust code without the help of rust-analyzer but the training material you see always seems to focus on the language and being agnostic about tooling. Editors and their extensions are so important when you are learning a language but newbies are expected to stumble upon the right ones by chance. It seems to be considered bad taste to steer beginners in one direction or the other when it comes to tooling. > “There are a lot of crates and finding the right one for the job requires a lot of effort or being very involved with the community.” My approach to to this it to look at the download counter (but then you need to know what to look for) and to ask friends in the community which kind of sucks for beginners. I’ve never really seen how I could benefit from something like copilot but if it could analyse my code and tell me that some of it could be replaced by calls to a popular crate then I would find that useful. As long as it wasn’t intrusive and didn’t make me feel bad.