Earlier quoted context omitted.
All / most of them are likely Servo contributors. Servo: https://servo.org/
Or rustc/libstd.
I think redox might be larger as well
Results of Rust Survey 2016 – early draft for internal usage
21–30 of 113 posts
Re: Results of Rust Survey 2016 – early draft for internal usage
#2248.8% of Rust users use nightly, 23 percentage points among them use both stable and nightly, which means 25.8% of Rust users use only nightly. Is it just me or does that seem exceedingly high? I'm guessing that a good deal of them are Rust language/core lib developers?
I personnally use nightly without being a core dev, because Rust is not available in Debian Stable so I just compile it from Git.
Re: Results of Rust Survey 2016 – early draft for internal usage
#23Please note that this is a leak of an early draft for the rust community teams internal usage and should be marked as such. Do consider all numbers undiscussed and not cleaned up for flaws (we'll document the cleanups and the reasonings). -- Florian // rust-community team
Sorry, I saw it on IRC and didn't know it wasn't supposed to be public
Re: Results of Rust Survey 2016 – early draft for internal usage
#24To author: would it be possible to improve the bar graphs, so that they were sorted by value, not by label? I believe it would make reading them much easier, and make them more informative [or, "deobfuscate" them]. (I mean those like "editors", etc., not "how long I know Rust" where the labels introduce sensible order.)
Re: Results of Rust Survey 2016 – early draft for internal usage
#2548.8% of Rust users use nightly, 23 percentage points among them use both stable and nightly, which means 25.8% of Rust users use only nightly. Is it just me or does that seem exceedingly high? I'm guessing that a good deal of them are Rust language/core lib developers?
Also a factor is that there are very useful libraries that either can only be used in nightly, or are more ergonomic to use in nightly. Usually because they rely on compiler internals or unstable language features. This is mentioned as one of the points under "Challenges for Rust".
Re: Results of Rust Survey 2016 – early draft for internal usage
#26> By large margin, users are often grabbing vim to do their Rust work in I would rather assume the reverse theory. Vim users are more likely to use new languages since they don't expect complex IDE support. Or maybe just: Early adopter and vim user correlates.
(disclaimer: I'm a vim user)
Also maybe because rust and vim appeal to the same argument of "performance/only come with the stuff you need"
Re: Results of Rust Survey 2016 – early draft for internal usage
#27Please note that this is a leak of an early draft for the rust community teams internal usage and should be marked as such. Do consider all numbers undiscussed and not cleaned up for flaws (we'll document the cleanups and the reasonings). -- Florian // rust-community team
Sorry, I saw it on IRC and didn't know it wasn't supposed to be public
We do most of our work in public, so it is public, just not intended for distribution :)
(In the case of the survey the analysis itself was conducted privately, because the data contains personally identifying information. But usually things are done in the public.)
Re: Results of Rust Survey 2016 – early draft for internal usage
#28Earlier quoted context omitted.
Note that we tried to publicize the survey amongst non-Rustaceans, so I expect most of these respondents are those who never used it in the first place. We got an overwhelming positive response, especially in the freeform comments. There's also: > Equally encouraging is seeing that once someone has become a Rust user, they tend to stick around and continue using it. One might expect a sharp drop-off if users became q…
Thanks for your work guys. I took part in the survey when I found it on Reddit. Yesterday I started my first project in two new technologies, Rust and GTK. That's completely different experience and perspective of designing code after years of C++(Qt) and Java(backend). Now I wish I was earlier adopter :)
Thank you! I'd love to hear more about your experience, though perhaps once you have worked a bit more on the project :)
Eh, early adoption is overrated -- you have to fight through lack of docs, lack of libraries, and general ecosystem issues, all while the language keeps changing underneath you :P
(Note that not everyone who works on Rust; or even who worked on this survey, is a guy)
Re: Results of Rust Survey 2016 – early draft for internal usage
#29Wow, ~180 people with projects more than 100000 lines.
All / most of them are likely Servo contributors. Servo: https://servo.org/
100k may seem like a lot, but if I do the sum of all lines of codes (exluding blank lines and comments) of the Rust projects where I'm the only contributor (or where other contributors are minor) I'm at around 61k lines of code.
Lines of code go up quicker than you think.
Re: Results of Rust Survey 2016 – early draft for internal usage
#30According to the survey, ~16% of people experience breakage with minor upgrades. Isn't this a pretty serious violation of semver?
I don't know the details in rust's case, but I wouldn't consider it a violation of semver if the code which broke in a minor update was doing bad things (maybe accidentally exploiting a bug or limitation in the language or implementation, probably by violating some requirement that wasn't checked properly, etc) and simply couldn't be correct code if left alone.