Interview
summary
Report shows a concrete adoption path: MapLibre uses a Rust core and a Martin tile server for fast map tiles, internal tiger teams build deliverables and FFI wrappers, CI/CD templates plus justfiles standardize local vs CI runs, and an intern rewrites a Python image pipeline to Rust in one week with another week to fix clippy warnings. Results: compiled-before-run checks shifted left detect ~70–80% of bugs, leadership funding for open-source maintenance speeds integration, embedded starts harder but standalone processes work.
AI-written summary · about
chapters (19)
- 0:00Rust adoption journey
- 1:29Open source to automotive with Rust
- 4:17Challenges in Rust adoption
- 7:31Management buy-in at Rivian
- 10:20Legacy code barriers in Rust
- 13:08Start slow, build infrastructure
- 15:54Meetups fail to drive Rust
- 18:00Tiger teams and collaboration
- 20:30Rust in embedded systems
- 22:35Mental model shifts in Rust
- 25:03Justfiles for Rust CI
- 26:50Teaching Rust with real projects
- 28:57Learning resources and reviews
- 31:09Open source in automotive
- 36:28Open source for automotive quality
- 37:32Onboarding with open source
- 40:42Funding open source contributions
- 42:24Contributing to open source
- 43:27Rust in automotive and SDV
related talks
35mCore Team Keynote
27mThe Wonderful World of Rust Tooling
45mCore Team Keynote
30mIntegrating Rust into Tor: Successes and Challenges
26mMoving to modern languages in long-living projects
20mAn Empirical Study of Rust-for-Linux: The Success, Dissatisfaction, and Compromise
38mPanel: Rust in reality
54mUnwrap()Ing Rust on Embedded Linux