Skip to content

Minor copy-edits in 2017 Survey post #198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 5, 2017
Merged

Minor copy-edits in 2017 Survey post #198

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions _posts/2017-09-05-Rust-2017-Survey-Results.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ author: Jonathan Turner

It's that time of the year, where we take a good look at how things are going by asking the community at large -- both Rust users and non-users. And wow, did you respond!

This year we had **5,368 responses**. *That's more than 2,000 responses than we had last year*!
This year we had **5,368 responses**. *That's over 2,000 more responses than we had last year*!

The scale of the feedback was both inspiring and humbling, and we've worked hard to read through all of your comments and suggestions. There were so many helpful ideas and experiences that people shared, and we truly do appreciate it. Without further ado, let's take a look.

Expand Down Expand Up @@ -36,7 +36,7 @@ Despite the rising amount of code developers are working with, we're seeing a sm

![Chart: 92.5% no, 7.5% yes](/images/2017-09-05-Rust-2017-Survey-Results/upgrade_stable.png "92.5% no, 7.5% yes")

In the last year, we made big strides in breakages caused by releases of the compiler. Last year, 16.2% respondents said that upgrading to a new stable Rust compiler broke their code. This year, that number has **fallen to 7.5% of respondents**. This is a huge improvement, and one we're proud of, though we'll continue working to push this down even further.
In the last year, we made big strides in breakages caused by releases of the compiler. Last year, 16.2% of respondents said that upgrading to a new stable Rust compiler broke their code. This year, that number has **fallen to 7.5% of respondents**. This is a huge improvement, and one we're proud of, though we'll continue working to push this down even further.

![Chart show strong support for nightly and current stable releases](/images/2017-09-05-Rust-2017-Survey-Results/which_version.png)

Expand Down Expand Up @@ -124,4 +124,4 @@ Finally, at the end of the survey we we provided a free-form area to talk about
# Conclusion

We're blown away by the response this year. Not only is this a much larger number of responses than we had last year, but we're also seeing a growing diversity in what people are using Rust for. Thank you so much for your thoughtful replies. We look forward to using your feedback, your suggestions, and your experience to help us plan for next year.