3 ms·
This is true in theory, but in practice is a nightmare. YMMV, but even small bits of python, Go, or (yes) Rust that have crept into the robotics stacks at the
by jvanderbot 2y ago
This is true in theory, but in practice is a nightmare.
YMMV, but even small bits of python, Go, or (yes) Rust that have crept into the robotics stacks at the various places I've worked have created problems for incoming new-hires, or for maintenance even for senior folks. Python less so than others, but python is challenging to deploy on vehicle, b/c of various hard and soft problems.
In particular, Rust interop with CPP is poor. Should I recompile all ros packages to allow me to call a few things in Rust? Not at this time.
I'm hopeful for the "Rust is robotics" movement, however https://robotics.rs/ https://robotics.rs/
The state of the field is so entrenched in CPP though there's more hope in embedded land with the widespread use of C.
- leoh 2y agoimo the issue is that doing academic training in robotics means doing whatever your advisor tells you to do and playing the academic rat-race game OR working in industry churning out features as fast as possible to keep your company alive, which essentially means that you are not going to be able to spend any meaningful time learning how to do FFI in Rust or Python or whatever. I think that's the real reason robotics software is in the dark ages. But then again, I'm not in the field and this is an armchair take. So yeah.