3 ms·
ROS can be an super enjoyable and productive environment to build software in. It gives you access to a set of common sensor and actuator drivers, motion planni
by sirsebastian 8y ago
ROS can be an super enjoyable and productive environment to build software in. It gives you access to a set of common sensor and actuator drivers, motion planning, navigation, perception libraries, and implementations of the latest IROS papers. I’ve seen it used to prototype lots of non-robotics applications too; really any local distributed system integrating, calibrating, and coordinating sensors. Personally I think the standardized data types it provides for robotics and perception data is one of its greatest assets [1], and could be a standards effort in itself. And it’s home to a great community.
But it definitely has its limits, especially as applications mature, and the ecosystem can feel siloed from the technology landscape evolving so quickly in, for example, backend distributed systems. Knowledge transfer between the robotics community and the software engineering happening in distributed systems, databases, gaming, web development, etc. is a huge untapped opportunity. Hit me up if you want to talk more about this!
[1] e.g. http://wiki.ros.org/sensor_msgs http://wiki.ros.org/sensor_msgs