3 ms·
They're referring to this[0] I believe, which is not glowing, but does seem mildly optimistic. Specifically: > For now, Chrome investment in Rust will remain a
by TheDong 6y ago
They're referring to this[0] I believe, which is not glowing, but does seem mildly optimistic. Specifically:
> For now, Chrome investment in Rust will remain a background investigation (mostly directed towards prototyping these tools and techniques). If we become convinced this sort of interoperability is possible, we’ll revisit widespread use of Rust in Chrome
[0]: https://www.chromium.org/Home/chromium-security/memory-safety/rust-and-c-interoperability https://www.chromium.org/Home/chromium-security/memory-safet...
- MaxBarraclough 6y agoRight, and their issues there all pertain to interoperability, not to issues with the Rust language and its implementation. They seem to view Rust as production-ready, and a language that would bring relevant benefits to the Chromium project, were it not for the C++ interoperability difficulties.
- fabrice_d 6y agoLooks like this will not happen soon: https://groups.google.com/a/chromium.org/g/blink-dev/c/gDA2SMPePv8 https://groups.google.com/a/chromium.org/g/blink-dev/c/gDA2S...
- est31 6y agoYes that's the same document I refer to as well. So nothing has changed. A "mildly optimistic" rejection is a rejection of Rust nonetheless. Rust is definitely not "on track" of being adopted in Chromium. For that you'd need more. Right now it's rather a "we are interested, maybe we'll add it". Also note that Chromium engineers also built some languages themselves that solve some of the same problems that Rust solves: https://github.com/google/wuffs https://github.com/google/wuffs