I hate ROS so much. Such a misguided effort given what we have with both common / existing and modern dev tooling. Sorry I don't use it now only because I can't test your replacement.
Good luck! Excited to see more stuff like this coming.
Thanks! Tell me about it… btw you don’t need to have a ROS stack to try Cerulion! Try giving the quickstart prompt to your agent and lmk if something breaks :)
I feel you! Too many seams, no sane defaults, and inefficiencies by design. We ended up keeping the nomenclature and message types due to entrenched design patterns. But we've tried to cut boilerplate and not gate performance deep behind nested docs pages. The tutorial graph is dead simple to set up and runs faster than the most optimized ROS2 code by orders of magnitude! And we've tried to bring this same performance to legacy ROS2 stacks as well :)
I hate ROS so much. Such a misguided effort given what we have with both common / existing and modern dev tooling. Sorry I don't use it now only because I can't test your replacement.
Good luck! Excited to see more stuff like this coming.
Thanks! Tell me about it… btw you don’t need to have a ROS stack to try Cerulion! Try giving the quickstart prompt to your agent and lmk if something breaks :)
I hate ROS so much as well:
- Robot Operating System - it is not even an operating system
- ROS Node - okay a process/thread that runs the application logic (but why name it as node? it is a service)
for ROS Node to talking to another ROS Node:
- I need a ROS topic
- I need a ROS Message
- in C++ I need rclcpp that is a C++ client
- which then uses rcl which is a C implementation
- it goes through a ROS Middleware (rmw) that is an abstract DDS (hey what is DDS)
- now you have many implementation choices, FastDDS, Cycloe DDS etc. which one should I pick?
- finally it would make some syscall
oh you want to build this with your application?
- use some weird command line called ros2 pkg create
- you need to use ament_cmake (what the heck is this?)
- and yet another tool called colcon to build the package
I feel you! Too many seams, no sane defaults, and inefficiencies by design. We ended up keeping the nomenclature and message types due to entrenched design patterns. But we've tried to cut boilerplate and not gate performance deep behind nested docs pages. The tutorial graph is dead simple to set up and runs faster than the most optimized ROS2 code by orders of magnitude! And we've tried to bring this same performance to legacy ROS2 stacks as well :)