Amen! That story mirrors my own experience. Neither approach is absolutely better or worse, they are each inherently better at solving different types of problems. Some realtime problems are just silly to try to handle abstracted away from the source of the events. But ROS, should not have a problem treating a low level integrated robot as a module by way of introduction to the "ROS way".
What ROS lacks is a simple clear path (development, tutorial, community outreach) to go from individual low level integrated sumo bots, RC, Arduino firmata, Vex, FIRST, etc to a useful ROS dev environment that handles swarm communication, coordination, and configuration based modular code update on Arduino devices in the field that are not running ROS.
---
[Visit Topic](
https://discourse.ros.org/t/why-dont-we-use-ros/3161/4) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)