Re:Robot Operating System 2.0: Ardent Apalone Release
by ratliffchrisb on Monday December 11, 2017 @12:10PM
(#15898383)
I think a lot of work has been undertaken for a ROS1->2 bridge. It should be feasible to use this to have ROS on a micro and bridge to an existing ROS 1 code base.
On the other hand, ROS2 aims to provide RTOS support and pluggable transport layers, which are rather serious benefits.
Also, their decision to abandon XML-based roslaunch is the right one: we had to roll out our own startup infrastructure as well, as it's much more convenient to have a definite init order with sequential checks and waits e.g. for hardware availability.