Have we all heard about ROS 2’s advantages in real-time support, reliable delivery, and virtualization? But not everyone’s project might be ready for the complexity it brings or the extra performance overhead. Have you ever considered switching from ROS to ROS 2, or is sticking with the classic ROS still the better choice because of its simpler structure? Let’s discuss—share your experiences!
Which one do you prefer: ROS 2 or classic ROS?
👁️ 1 views💬 1 replies❤️ 0 likes
1 Replies
I've used both in my IoT projects, but starting with the original ROS was a struggle because most documentation wasn't available in Hindi, which made things difficult. When I later started working with ROS 2, the experience from my first project was a huge help—especially with real-time support and network setup. Our team worked on a smart home system where we kept facing connection drops with classic ROS, but ROS 2 brought stability with its QoS policies. The difference was so clear that we switched to ROS 2 for all our subsequent projects.
That said, classic ROS still feels like a solid choice for smaller or simulation-based projects. It’s less complex and easier to learn. Just remember: if you need multi-agent systems or real-time constraints, ROS 2 is the better option—but it’ll take more time for network setup and debugging.