> a C developer might say. “But Rust is still a very large language, and only growing larger over time.” The C developer would be right. Nice article. As someo

> a C developer might say. “But Rust is still a very large language, and only growing larger over time.” The C developer would be right. Nice article. As someone who uses Rust on embedded, this is a concern I share - especially regarding async/await, which this article mentions specifically. I see my (and for others of a like mind) path forward is using an explicitly-defined-at-project-level subset of Rust... In the vein of what we see in C++. This use of a dialect has drawbacks for newcomers to a code base, but I prefer it to the alternative of not mitigating the downsides of a large language. Perhaps this prediction won't turn out to be true, and the Rust language will slow its expansion.