Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But the approach here is "write new code in rust", not rewrite.


Google rewrote Android's Bluetooth stack in Rust.


Also mentioned:

  Chromium: Parsers for PNG, JSON, and web fonts have been replaced with memory-safe implementations in Rust


Eh, I don't think it's actually one or the other. Google has taken on rewriting some more problematic components in rust. See for example:

Binder kernel driver: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Media codecs: https://www.androidauthority.com/android-16-in-process-softw...


This is also happening at Microsoft:

> Rewriting SymCrypt in Rust to modernize Microsoft’s cryptographic library

https://www.microsoft.com/en-us/research/blog/rewriting-symc...


Yeah, there's also a freetype replacement https://github.com/googlefonts/fontations

I think they're trying to avoid rewriting things for no reason though. The things being rewritten tend to have a history of security problems or other issues that would be cause for a rewrite even if it wasn't in Rust.


That ends up being "rewrite it in Rust" because new code includes changes to existing code. A nice thing about Rust is that you can generally rewrite things piecewise there's no need to switch everything at once.


Sure, but at a macro level the approach is still to "rewrite" Android subsystems in Rust. Just slowly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: