Robot Operating System – A flexible framework for writing robot software
My experience with ROS has been suboptimal. It&#x27;s a collection of incompatible, outdated and buggy tools that communicate with each other via a single-point of failure (roscore) using a pub&#x2F;sub mechanism.<p>Furthermore they use their <i>own</i> build system (catkin, WHY?), define their <i>own</i> IDL (WHY?), use their <i>own</i> dependency system (rosdep, WHY?) and even mess with your Bash environment.<p>I appreciate their effort and it is really hard to make a system that interfaces with all kinds of different robots and hardware, but I don&#x27;t understand why they don&#x27;t exploit existing high-quality solutions for the &quot;not-robot-related&quot; parts of their system. At the moment I don&#x27;t think I would like to have ROS run a potential self-driving car.