• This is another post in our series covering what we learned through the Vision Doc process. • In our first post, we described the overall approach and what we learned about doing user research. • In our second post, we explored what people love about Rust. • This post goes deep on one domain: safety-critical software. • When we set out on the Vision Doc work, one area we wanted to explore in depth was safety-critical systems: software where malfunction can result in injury, loss of life, or environmental harm. • Think vehicles, airplanes, medical devices, industrial automation.
Article Summaries:
- This is another post in our series covering what we learned through the Vision Doc process. In our first post, we described the overall approach and what we learned about doing user research. In our second post, we explored what people love about Rust. This post goes deep on one domain: safety-critical software. When we set out on the Vision Doc work, one area we wanted to explore in depth was safety-critical systems: software where malfunction can result in injury, loss of life, or environmental harm. Think vehicles, airplanes, medical devices, industrial automation. We spoke with engineers a
- The post examines Rust’s fit for safety‑critical software, drawing on interviews with OEMs, integrators, and suppliers in automotive, industrial, aerospace, and medical fields. It highlights that Rust’s compiler guarantees cover many safety‑engineering concerns, yet the ecosystem lags once projects move beyond prototypes: there is no MATLAB/Simulink code generation, no Rust‑compatible OSEK or AUTOSAR Classic RTOS, and qualification tooling is still maturing. Despite these gaps, Rust is already in production-used in IEC 61508 SIL 2 mobile‑robotics systems and IEC 62304 Class B medical devices-showing that real‑world deployments are possible while the ecosystem continues to evolve.
Sources: