zlacker

[parent] [thread] 4 comments
1. atemer+(OP)[view] [source] 2024-04-26 10:38:19
I wonder what will happen if one starts developing, say, a RTOS for cruise missiles in Rust. Will this be controversial enough to destroy the Rust community?
replies(2): >>Macha+6S >>lr1970+bT
2. Macha+6S[view] [source] 2024-04-26 16:11:12
>>atemer+(OP)
Rust has had at times multiple members of its leadership team employed by Palantir and not imploded, so probably not.
replies(1): >>Aerbil+oE6
3. lr1970+bT[view] [source] 2024-04-26 16:16:48
>>atemer+(OP)
> I wonder what will happen if one starts developing, say, a RTOS for cruise missiles in Rust.

It is already happening and with the help of some known personalities in the Rust community [0].

[0] https://www.linkedin.com/in/jonhoo/

◧◩
4. Aerbil+oE6[view] [source] [discussion] 2024-04-29 00:48:35
>>Macha+6S
Sheesh. And you can't write a reproducible compiler for Rust either, because every version of rustc was compiled with the previous version. What are the chances there isn't a backdoor?
replies(1): >>stevek+Y27
◧◩◪
5. stevek+Y27[view] [source] [discussion] 2024-04-29 05:34:47
>>Aerbil+oE6
> What are the chances there isn't a backdoor?

mrustc, an independent implementation, has produced identical output.

> rustc bootstrap tested and validated (1.19.0 isn't fully repeatable, but later versions are)

https://github.com/thepowersgang/mrustc?tab=readme-ov-file#p...

This means you'd have to land the same attack in both mrustc and rustc, making the possibility infinitesimally small.

[go to top]