|
|
|
|
|
|
by steveklabnik
2290 days ago
|
|
|
I think one of the hard things about making suggestions about how to do a thing like this is that it's unfalsifiable. I'm not suggesting that only things that are falsifiable are worthwhile, but like, let's take what you're saying here at face value: Rust was evangelized successfully. What we can't know is, could we have done a better job than we did? Did some of those choices that I or whoever else would suggest as a best practice actually harm the adoption of the language? How can we tell the difference? |
|
|
I was more suggesting that there's a story about how Rust became what it is today, and the active guidance that members of the core team(s) took on to take it there. It's a story I'd like to read, that's all.
The questions you bring up are very good ones, and they're relevant to anyone developing technology like a programming language - be it a FOSS project, a creative tool, whatever. But I think from a literary perspective it wouldn't be the job of the person telling the story to answer them, but for the reader to decide for themselves.