Daniel Micay on Twitter: "@_watzon @GrapheneOS I haven't done that. See https://t.co/av83jbnLs8. GrapheneOS uses memory safe languages as the default choice. It didn't make sense to use Rust for https://t.co/XgCPXc1mUy. It would only make correctness harder rather than easier in this case due to the immaturity of unsafe Rust." / Twitter

so several of us are wondering: why did you choose C over Rust for

@GrapheneOS

? Was it because a lot of ASOP is already in C or was it a more intentional choice?

Replying to

and

I haven't done that. See grapheneos.org/build#developm. GrapheneOS uses memory safe languages as the default choice. It didn't make sense to use Rust for github.com/GrapheneOS/har. It would only make correctness harder rather than easier in this case due to the immaturity of unsafe Rust.

github.com

GitHub - GrapheneOS/hardened_malloc: Hardened allocator designed for modern systems. It has...

Hardened allocator designed for modern systems. It has integration into Android's Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-base...

10:53 AM · Aug 4, 2019Twitter Web App

Replying to

and

Thanks for the quick reply. I didn't realize you were using rust and neither did anyone else I was talking with 😂 good to see it hasn't been abandoned

Conversation