ROS (Robot Operating System)

ROS isn't really an operating system — it's the toolkit that lets the dozens of programs inside a robot talk to each other. It's how nearly every modern research robot is built.

Why a robot needs ROS

A modern robot is not one program. It's many programs running at once:

• One program reads the camera
• Another reads the lidar
• Another fuses the two readings into a 3D map
• Another plans a path through that map
• Another sends velocity commands to the motors
• Another logs everything for debugging

If you wrote all of this as a single program, any change in one part would risk breaking the others. ROS is the plumbing that keeps them separate — yet able to talk.

The three big ideas

Nodes. Each program is a "node". Each node has one job. Each node runs in its own process. A typical robot has 20-50 nodes.

Topics. Nodes publish messages onto named "topics" — /camera/image, /lidar/scan, /cmd_vel. Other nodes subscribe to topics they care about. It's a publish-subscribe pattern. Nodes never address each other directly — they only know the topic names.

Services and actions. Two more communication patterns: services for quick request-response, actions for long-running goals like "drive to this location."

That's basically all of ROS in three concepts.

ROS 1 vs. ROS 2

ROS 1 was released in 2007 by Willow Garage. It powered an entire generation of robotics research but had real limitations: a single point of failure (the ROS master), poor support for real-time control, weak security.

ROS 2 (released 2018) rebuilt the same ideas on top of DDS (Data Distribution Service) — an industrial-grade pub/sub middleware. It has no master, supports real-time guarantees, runs on tiny embedded devices, and has security built in. As of 2026, all new robotics projects start with ROS 2. ROS 1 is officially end-of-life.

Who uses it

Boston Dynamics' research demos. NASA's Robonaut. Most autonomous mobile robots in warehouses. Most university robotics courses. Most quadruped startups. The Indian robotics ecosystem leans heavily on ROS 2 too — it's free, open-source, and reduces engineering time by months.

Notably not using ROS: Tesla, Apple, most automotive self-driving stacks. They use custom in-house frameworks because their products are commercial and they want full control of every byte.

To see ROS 2 in action, that's Forge 01 in our learning track — the 6-lesson "ROS 2 from scratch" course.