Bridging robotics and systems programming:Why Copper is a game changer
summary
Copper is a Rust SDK and runtime that replaces ROS-style async messaging with a compile-time scheduled game-loop, producing a deterministic execution plan and enabling proc-macro-generated runtime code. Benchmarks claim two orders of magnitude faster latency versus ROS and 12,000× faster logging with a 12× advantage on MCAP. It supports cross-compilation, integrates with Bevy/Avian/zeno/rerun, targets gradual C++ interop, and has a concrete no_std/embedded roadmap while compile times remain a practical pain point.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:27Who this talk is for
- 3:19Roboticists' challenges today
- 4:22Introducing Copper demo
- 6:54ROS limitations and design
- 9:23Why Copper in Rust
- 10:31Copper’s game-engine vision
- 12:43Copper’s determinism and performance
- 14:28Deployment and optimization
- 15:32Kunic Sensei and DX
- 17:39Copper’s Rust ecosystem
- 19:30Rust advantages for robotics
- 21:19Selling Rust to roboticists
- 23:06Compile times and Windows issues
- 24:31C++ libraries and ROS interop
- 25:58User resistance to change
- 27:09Q&A: compile times & distributed systems
- 29:18Q&A: embedded support plans
related talks
39mReal-Time Rust in Robotics
41m"Rust for Robotics: Safer, Faster Systems for Autonomous Applications"
55m“C++ in Open Source Robotics"
20m"Rust in Motion: Building Reliable and Performant Robotics Systems"
41mCap'n Proto and Rust: Type Systems for Sharing
35mAll aboard the Rust (electric freight) train!
36mFun with Rusty Robots
36mScaling robots -