Android 14 is the third main Android launch with Rust assist. We’re already seeing a number of advantages:
These constructive early outcomes offered an attractive motivation to extend the pace and scope of Rust adoption. We hoped to perform this by investing closely in coaching to broaden from the early adopters.
Early adopters are sometimes keen to simply accept extra threat to check out a brand new expertise. They know there might be some inconveniences and a steep studying curve however are keen to study, usually on their very own time.
Scaling up Rust adoption required transferring past early adopters. For that we have to guarantee a baseline stage of consolation and productiveness inside a set time period. An necessary a part of our technique for undertaking this was coaching. Sadly, the kind of coaching we needed to supply merely didn’t exist. We made the choice to put in writing and implement our personal Rust coaching.
Our objectives for the coaching had been to:
- Shortly ramp up engineers: It’s arduous to take folks away from their common work for an extended time period, so we aimed to supply a strong basis for utilizing Rust in days, not weeks. We couldn’t make anyone a Rust skilled in so little time, however we might give folks the instruments and basis wanted to be productive whereas they continued to develop. The aim is to allow folks to make use of Rust to be productive members of their groups. The time constraints meant we couldn’t educate folks programming from scratch; we additionally determined to not educate macros or unsafe Rust intimately.
- Make it participating (and enjoyable!): We needed folks to see a whole lot of Rust whereas additionally getting hands-on expertise. Given the scope and time constraints talked about above, the coaching was essentially information-dense. This referred to as for an interactive setting the place folks might shortly ask inquiries to the teacher. Analysis reveals that retention improves when folks can shortly confirm assumptions and follow new ideas.
- Make it related for Android: The Android-specific tooling for Rust was already documented, however we needed to indicate engineers learn how to use it by way of labored examples. We additionally needed to doc rising requirements, resembling utilizing thiserror and anyhow crates for error dealing with. Lastly, as a result of Rust is a brand new language within the Android Platform (AOSP), we wanted to indicate learn how to interoperate with present languages resembling Java and C++.
With these three objectives as a place to begin, we regarded on the present materials and out there instruments.
Current Materials
Documentation is a key worth of the Rust group and there are various nice sources out there for studying Rust. First, there’s the freely out there Rust E book, which covers virtually the entire language. Second, the usual library is extensively documented.
As a result of we knew our audience, we might toughen assumptions than most materials discovered on-line. We created the course for engineers with a minimum of 2–3 years of coding expertise in both C, C++, or Java. This allowed us to maneuver shortly when explaining ideas acquainted to our viewers, resembling “management circulate”, “stack vs heap”, and “strategies”. Individuals with different backgrounds can study Rust from the numerous different sources freely out there on-line.
Expertise
Free of charge-form documentation, mdBook has grow to be the de facto customary within the Rust group. It’s used for official documentation such because the Rust E book and Rust Reference.
A very fascinating characteristic is the power to embed executable snippets of Rust code. That is key to creating the coaching participating because the code will be edited reside and executed immediately within the slides:
Along with being a well-recognized group customary, mdBook provides the next necessary options:
- Maintainability:
mdbook take a look at
compiles and executes each code snippet within the course. This allowed us to evolve the category over time whereas guaranteeing that we all the time confirmed legitimate code to the contributors. - Extensibility: mdBook has a plugin system which allowed us to increase the instrument as wanted. We relied on this characteristic for translations and ASCII artwork diagrams.
These options made it straightforward for us to decide on mdBook. Whereas mdBook isn’t designed for displays, the output regarded OK on a projector once we restricted the vertical dimension of every web page.
Supporting Translations
Android has builders and OEM companions in lots of international locations. It’s essential that they will adapt present Rust code in AOSP to suit their wants. To assist translations, we developed mdbook-i18n-helpers. Help for multilingual documentation has been a group want since 2015 and we’re glad to see the plugins being adopted by a number of different tasks to supply maintainable multilingual documentation for everyone.
With the expertise and format nailed down, we began writing the course. We roughly adopted the define from the Rust E book because it coated most of what we have to cowl. This gave us a 3 day course which we referred to as Rust Fundamentals. We designed it to run for 3 days for 5 hours a day and embody Rust syntax, semantics, and necessary ideas resembling traits, generics, and error dealing with.
We then prolonged Rust Fundamentals with three deep dives:
- Rust in Android: a half-day course on utilizing Rust for AOSP improvement. It contains interoperability with C, C++, and Java.
- Naked-metal Rust: a full-day class on utilizing Rust for bare-metal improvement. Android units ship vital quantities of firmware. These elements are sometimes foundational in nature (for instance, the bootloader, which establishes the belief for the remainder of the system), thus they should be safe.
- Concurrency in Rust: a full-day class on concurrency in Rust. We cowl each multithreading with blocking synchronization primitives (resembling mutexes) and async/await concurrency (cooperative multitasking utilizing futures).
A big set of in-house and group translators have helped translate the course into a number of languages. The complete translations had been Brazilian Portuguese and Korean. We’re engaged on Simplified Chinese language and Conventional Chinese language translations as nicely.
Course Reception
We began educating the category in late 2022. In 2023, we employed a vendor, Immunant, to show the vast majority of lessons for Android engineers. This was necessary for scalability and for high quality: devoted instructors quickly found the place the course contributors struggled and will adapt the supply. As well as, over 30 Googlers have taught the course worldwide.
Greater than 500 Google engineers have taken the category. Suggestions has been very constructive: 96% of contributors agreed it was price their time. Individuals persistently instructed us that they beloved the interactive model, highlighting the way it helped to have the ability to ask clarifying questions at any time. Instructors famous that individuals gave the course their undivided consideration as soon as they realized it was reside. Dwell-coding calls for so much from the teacher, however it’s price it because of the excessive engagement it achieves.
Most significantly, folks exited this course and had been capable of be instantly productive with Rust of their day jobs. When contributors had been requested three months later, they confirmed that they had been capable of write and evaluate Rust code. This matched the outcomes from the a lot bigger survey we made in 2022.
We now have been educating Rust lessons at Google for a 12 months now. There are some things that we wish to enhance: higher matter ordering, extra workout routines, and extra speaker notes. We might additionally like to increase the course with extra deep dives. Pull requests are very welcome!
The complete course is obtainable without spending a dime at https://google.github.io/comprehensive-rust/. We’re thrilled to see folks beginning to use Complete Rust for lessons around the globe. We hope it may be a helpful useful resource for the Rust group and that it’s going to assist each small and enormous groups get began on their Rust journey!
We’re grateful to the 190+ contributors from all around the world who created greater than 1,000 pull requests and points on GitHub. Their bug experiences, fixes, and suggestions improved the course in numerous methods. This contains the 50+ individuals who labored arduous on writing and sustaining the numerous translations.
Particular because of Andrew Walbran for writing Naked-metal Rust and to Razieh Behjati, Dustin Mitchell, and Alexandre Senges for writing Concurrency in Rust.
We additionally owe a substantial amount of because of the numerous volunteer instructors at Google who’ve been spending their time educating lessons across the globe. Your suggestions has helped form the course.
Lastly, because of Jeffrey Vander Stoep, Ivan Lozano, Matthew Maurer, Dmytro Hrybenko, and Lars Bergstrom for offering suggestions on this submit.