4 ms·

Do user studies. It's pretty much unheard of, but nearly every open source project would benefit far more from a week of watching potential contributors trying

Do user studies. It's pretty much unheard of, but nearly every open source project would benefit far more from a week of watching potential contributors trying to get up to speed than it would from making sure the project roadmap is delivered a week sooner. That's my claim for projects in general, and what you're asking for re Rust is a little different, but the approach can applied there, too. Focus on everything from navigating the project website and other docs, to interactions with the tools that make up the "ecosystem", to programmer expectations that could shape the language (with the latter actually being the least important). Don't trust users to self-report. Don't overestimate your ability to make a combined diagnosis and prescription, and don't underestimate how much silent resignation is killing your adoption rate. Observe and work off real notes.

mattip 11y ago
Has this been done for any project? I am interested in seeing the setup used, resulting reports, and changes instituted
charlieflowers 11y ago
This is the most insightful comment in the discussion. It should have been obvious, but it wasn't until you posted it. First, design a sound language that solves problems other languages don't (done). Then, optimize for adoption ... because the world only benefits from that new language once adoption really takes off. Rust has done half the job really well. And a decent start on the second half -- mainly because the first half was done so well. But if the Rust team were to prioritze adoption the way the parent post espouses, they'd be changing their priorities significantly, and it's probably the most effective way to make sure Rust fulfills its potential.
- steveklabnik 11y ago
  We have done a lot of things to prioritize adoption, though we could do better. We have done some almost-studies like this: we had a series of conference calls with companies using production Rust specifically to work on their pain points, for example.

mattip 11y ago

Has this been done for any project? I am interested in seeing the setup used, resulting reports, and changes instituted

charlieflowers 11y ago

This is the most insightful comment in the discussion. It should have been obvious, but it wasn't until you posted it. First, design a sound language that solves problems other languages don't (done). Then, optimize for adoption ... because the world only benefits from that new language once adoption really takes off. Rust has done half the job really well. And a decent start on the second half -- mainly because the first half was done so well. But if the Rust team were to prioritze adoption the way the parent post espouses, they'd be changing their priorities significantly, and it's probably the most effective way to make sure Rust fulfills its potential.

steveklabnik 11y ago
We have done a lot of things to prioritize adoption, though we could do better. We have done some almost-studies like this: we had a series of conference calls with companies using production Rust specifically to work on their pain points, for example.