|Daily Rust Use Increases, Survey Finds|
|Written by Kay Ewbank|
|Monday, 04 May 2020|
The results of the fourth annual Rust Survey have been released, covering the responses of almost 4,000 developers. Rust began life at Mozilla and has been around for ten years. The latest release is Rust 1.42.
The aim of Rust is to offer a safe, fast and concurrent language without having a garbage collector. It is constructed so that problems are detected at compile time so that it can be used safely for systems programming.
The survey was available in 14 different languages, and while nearly 70 percent answered in English, 10.8 percent of respondents answered in Chinese. This might explain why one of the main answers to what respondents would like to see improved was availability of documentation in other languages, including Chinese. The Rust development team is currently hard at work on translating the documentation.
In terms of how often the respondents use Rust and what they use it for, 27.6 percent now use Rust daily, up from 17.5 percent in 2017. 40.9 percent use Rust weekly, and 19.8 percent do so monthly. The most common industry sector for full-time Rust developers was backend web development., followed by distributed and embedded systems.
A major focus of the survey was how various aspects have improved (or not) over the past year, and the respondents were clear that not everything has got better. Most people thought adoption levels had seen 'some improvement', but asked about compile time, the majority of responses were split between 'slight' and 'some' improvement, with far fewer people - under 250 of the 4000 respondents - thinking things had got a lot better.
People were even less convinced about GUI development improvements, with most opting for 'don't know' as an answer, and the rest mainly split between 'no change' and 'slight improvement'.
Areas where respondents felt there had been real improvements include async I/O, IDE experience, library support and tools & support.
or email your comment to: firstname.lastname@example.org