studio

Congrats to the Open Robotics team and everyone who contributed to this release! Calling out a couple changes I'm excited about that we (Foxglove) helped contribute to: - MCAP is now the default logging format in Rosbag2[0]. This is a much more performant and configurable format than the previous default (SQLite-based). SQLite is still a fully supported alternative. - Message type definitions (schemas) can now be exchanged at runtime[1]. This means that tools such as rosbag2, or visualization tools such as Foxglove Studio[2] can now communicate with a ROS system over the network without needing a copy of the source code or complete ROS workspace. [0] https://github.com/ros2/rosbag2/pull/1160 [1] https://github.com/ros2/ros2/issues/1159 [2] https://github.com/foxglove/studio

> Especially a tool like RViz is always missing. And in many many robotics video I see (of a moderately complex robot), there's ROS's RViz on some screen. I would love the future robotics development stack to be more modular, so that (for example) future middleware solutions don't need to also bundle their own visualization software. This was direct inspiration for creating Foxglove Studio[0] for visualization and MCAP[1] for logging - both work great with ROS, or equally well without it. [0] https://github.com/foxglove/studio [1] https://github.com/foxglove/mcap