-
Couldn't load subscription status.
- Fork 314
Draft of 2018 survey results #291
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.
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
Conversation
|
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
|
|
||
| The percentage of people who see a breakage during a routine compiler update has stayed the same since last year, with 7.4% saying they’ve experienced breakage. | ||
|
|
||
|  |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If 5991 users took the survey and assuming most of them responded to the previous question, then 7.4% * 5991 = 443 users have experienced breakage from a stable compiler upgrade. This chart shows about twice that many responses (~900). Given that the question is worded "if so", let's omit answers from users who have not experienced breakage.
If the extra 450 people all responded "1", then this becomes a very different graph.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dtolnay - sometimes people selected "1" to mean "it didn't happen to me" in addition to "it happened to me and I fixed it". I could pivot and remove the extraneous ones.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix typo Co-Authored-By: jonathandturner <jonathandturner@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few wording clarifications, and a few follow-up questions that I immediately had that other readers might have, that we may or may not have answers for :)
|
|
||
|  | ||
|
|
||
| We’re seeing similar numbers in users of the current stable release since last year. Perhaps surprisingly, we’re continuing to see a rise in the number of users who use the Nightly compiler in their workflow. For the second year in a row, Nightly usage has continued to rise, and is now over 56% (up from 51.6% of last year). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we happen to ask why folks use nightly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We did! I put some examples in the latest draft.
|
|
||
|  | ||
|
|
||
| Looking closer at these users who feel unproductive in Rust, only about 25% are in their first month of use. The challenge here is to find ways to help bridge users to productivity so they don't get stuck. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we happen to ask why folks feel unproductive, specifically?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We didn't ask, unfortunately

No description provided.