3 ms·
ROS 2 is in this uncomfortable place that python3 was in for many years. It's clearly the future. Everybody wants to move to it. But too many of the useful l
by oofbey 5y ago
ROS 2 is in this uncomfortable place that python3 was in for many years. It's clearly the future. Everybody wants to move to it. But too many of the useful libraries haven't been ported over yet, so people mostly stick with ROS1.
We might be getting close to a tipping point. I hope so. But it's probably still 1-4 years out.
- palaber 5y agoIt's unfortunate because there was no need at all for it to be such a painful transition. Even when you do have all the packages you need available in ROS 2 the experience is still notably more complex and less developer friendly. Just consider what it says that at ROSCon this year a 3rd-party library was highlighted that lets ROS 2 python nodes use the ROS 1 API, almost four years after the first official ROS 2 release.
- Maven911 5y agoDo you work on the robotics industry professionally by any chance and is ROS used there?
- deleted 5y ago[deleted]