I'd love to use something other than ROS2, if for no other reason than to get rid of the dependency hell and the convoluted build system. But there are a lot of nodes and drivers out there for ROS already. It's a chicken and egg thing because people aren't going to write drivers unless there are enough users, and it's hard to get users without drivers. It looks like their business model is to give away the OS and mak…
ROS is, in my opinion, dying on the industry front. * It is a dependency hell * It is resource-heavy on embedded systems * It is too slow for real-time, high speed control loops * Huge chunks of it are maintained by hobbyists and far behind the state of the art (e.g. the entire navigation stack) * As robotics moves toward end-to-end AI systems, stuff needs to stay on GPU memory, not shuttled back and forth across pro…
Re: PeppyOS: A simpler alternative to ROS 2 (now with containers support)
#41What alternatives there are that exist and can replace ROS? I imagine that not all companies are using ROS, however, I'm not in that field exactly so I don't know. I always thought that the quality of that code is mediocre at best.