dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify production framing

This commit is contained in:
Aaron Turon 2016-10-21 19:27:28 -07:00
parent a2cb436161
commit c403028cc4
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
text/0000-roadmap-2017.md
View File

@ -29,7 +29,7 @@ The proposal is based on the [2016 survey], systematic outreach, direct conversa
There's no end of possible improvements to Rust—so what do we use to guide our
thinking?
The core team has tended to view things not in terms of particular features or
The core team has tended to view our strategy not in terms of particular features or
aesthetic goals, but instead in terms of **making Rust successful while staying
true to its core values**. This basic sentiment underlies much of the proposed
roadmap, so let's unpack it a bit.
@ -66,6 +66,12 @@ valuable new way of programming, we should be seeing that benefit in "the real
world", in production uses that are significant enough to help sustain Rust's
development.
That's not to say we should expect to see this usage *immediately*; there's a
long pipeline for technology adoption, so the effects of our work can take a
while to appear. The framing here is about our long-term aims. We should be
making investments in Rust today that will position it well for this kind of
success in the future.
### The obstacles to success
At this point, we have a fair amount of data about how Rust is reaching its