Add state of Rust survey 2016 #105
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @rust-lang (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
This is exceedingly minor, but usually it's one space after the period, not two, and 80 cols. I'm not sure if it's worth the time to fix.... |
|
@steveklabnik - that's how you know I'm old school ;) |
| ![Using Rust at work in future][rust_at_work_future] | ||
| </center> | ||
|
|
||
| Of those not currently using Rust at work, more than 40% plan to being able to use Rust at work. This will help carry Rust to more places and in more areas. Speaking of carrying to more areas, we saw a wide variety of job domains represented in the survey: |
There was a problem hiding this comment.
"plan on being able to use"
|
I love it! |
|
|
||
| > "Proper IDE support (hard to get it accepted at work for that reason)" | ||
|
|
||
|
|
There was a problem hiding this comment.
extremely minor: there's an extra newline here
|
👍 |
|
👍 |
|
My minimum threshold for surveys is 3087 respondents, so we may want to rethink all our analysis here. In other words, looks great to me! |
This is the blog post for the "State of Rust Survey 2016"
r? @rust-lang/core
cc @skade @carols10cents @bstrie @Manishearth @erickt @brson