Re:
by lakshays on Thursday November 12, 2026 @09:48PM
(#50477467)
I feel you! Too many seams, no sane defaults, and inefficiencies by design. We ended up keeping the nomenclature and message types due to entrenched design patterns. But we've tried to cut boilerplate and not gate performance deep behind nested docs pages. The tutorial graph is dead simple to set up and runs faster than the most optimized ROS2 code by orders of magnitude! And we've tried to bring this same performance to legacy ROS2 stacks as well :)
[ Parent
| on HN ]
There are no comments on this comment yet.