I built this during robotics competitions and internships where I kept
hitting the same friction: just to publish sensor data between two
machines, ROS2 requires writing .msg files, editing CMakeLists.txt,
running colcon build, sourcing setup scripts...
So I made NitROS — zero config pub/sub with auto-discovery (mDNS),
built-in compression for images/point clouds, and support for numpy/PyTorch
out of the box.
Took about 3 days to build the initial version. It's still early but
has been useful enough in my own projects to share.
I'm not claiming this replaces ROS2 — it doesn't have TF, URDF, action
servers, etc. It's just for when you want simple pub/sub to work without
fighting a build system.
Would love feedback, especially on edge cases or network scenarios I
haven't tested.
Hey HN, I'm Samuel, creator of NitROS.
I built this during robotics competitions and internships where I kept hitting the same friction: just to publish sensor data between two machines, ROS2 requires writing .msg files, editing CMakeLists.txt, running colcon build, sourcing setup scripts...
So I made NitROS — zero config pub/sub with auto-discovery (mDNS), built-in compression for images/point clouds, and support for numpy/PyTorch out of the box.
Took about 3 days to build the initial version. It's still early but has been useful enough in my own projects to share.
I'm not claiming this replaces ROS2 — it doesn't have TF, URDF, action servers, etc. It's just for when you want simple pub/sub to work without fighting a build system.
Would love feedback, especially on edge cases or network scenarios I haven't tested.