2 ms·
> your mistake was going for ROS 2 which is by any objective metric a complete trainwreck compared to ROS 1 Sometimes you don't have a choice. I prefer to stic
by ModernMech 2y ago
> your mistake was going for ROS 2 which is by any objective metric a complete trainwreck compared to ROS 1
Sometimes you don't have a choice. I prefer to stick with ROS 1 but the org I was working with insisted on running ROS2 for everything. The only thing worse than running ROS2 is running ROS2 installed next to ROS1 and trying to work with both.
- moffkalast 2y agoI mean it is a huge dilemma right now. Noetic is incredibly stable, it has lots of packages, language models all know it in detail, any problems are noted and workarounds known... and support will be cut in a bit over a year. Kind of the exact opposite is the case for Jazzy really. I think it really hinges on the date you need to have working code on and how long you intend to maintain it I guess. For a company building up its software with a 2 year latency in deployment it probably makes more sense to develop slowly along with ROS 2 and hope for the best. Also don't get me started on Gazebo Classic/11 vs Ignition lol, that's a similar can of worms right there.