Changes

One major issue with Rust relates to personnel. * There is a wide variety of experience levels within Mozilla, for both coding and reviewing. Also, * Rust's learning curve is steep at the start, which can be intimidating.

* Compile times are currently very Compilation is slow and compilation uses too much memory.* Crossing the C++/Rust boundary layer can be difficult, and is relatively slow due to no inlining.** Bindgen can be tricky, especially working around clang bugs in different versions See "Blockers and on different platforms* Android is currently [https://forge.rust-lang.org/platform-support.html not a Tier 1 platform].** rillian: obstacles"As I understand it, the problem is no one has set up tests on a cloud service, so there's no way below for upstream to gate work on Android regressions. Qemu emulation is too slow. There aren't many services with arm support, but there are a couple of new options. If someone does the more details about work of setting something up we should be able being done to get the Rust team to adopt it."* Integration with Gecko often requires adding wrapper/glue code. Such code is typically valuable and reusable, however.* Sharing components between Gecko and Servo is difficult.** The workflow is annoying and inefficient. Furthermore, permission to land directly on autoland is sometimes needed to fix problems, but few people have that.*** vcs-sync/Phabricator/Lando will hopefully fix this.** There are continuous integration mismatches.** Servo CI is potentially under-resourced.** This is not relevant for Gecko-only Rust components, howeverremedy these weaknesses.