Thanks again! The way you phrase it, managing a large-scale public open source project sure sounds like a good balance of challenging and exciting!

Hah, clicking on the link led me to the realization that I had already seen that talk before! But I keep getting amazed at how much Mozilla has invested into this project :)

A large fraction of the Rust team works at Mozilla, and I've always been a bit curious about how that came to be. I mean, I work with some MLOCs of hairy legacy C++ code at work, so I can understand the desire to have a better systems programming language, but there is a difference between dreaming that and hiring quite a large team to actually make it happen! Could you give me a bit of perspective on this?

Thanks!

Also, to expand a bit on this question, how do you interact with people who have a good intuition when it comes to language ideas, but would not translate these ideas into a formal RFC form due to fear of general lack of spec writing skills? There are plenty of people out there who are better at thinking or coding than technical writing.

There are lots of great language improvement ideas flying around in the RFC repo. Non-lexical lifetimes, module system revamp, const fns, variadic generics, extensions to the trait system, and so many others... I assume there are a lot more people proposing ideas than people working on the language, so how do you manage to cope with the flux, examine all of the proposals, and prioritize those that get accepted for implementation?