Discussion

The robotics framework for simplified robot development.

Jenzaah: What makes this better than HORUS? Also Rust based, and opensource already.

LatticeAnimal: IIRC, the ROS UR controller runs at 200Hz and we’ve had arms crash when they run much slower than that.The website claims “30hz polling rate”, “2ms latency”. Not sure if that is a best case or just for that demo.

digikata: Crash? The software, or physically? A 200Hz as a min control loop rate seems on the fast side as a general default, but it all depends on the control environment - and I may be biased as I've done a lot more bare silicon controls than ROS.

ijustlovemath: There's no actual source for this, just some examples

blensor: Looking through the website and github, it looks a bit premature to post at all. I don't have too much love for ROS personally but that claim the title is making is quite bold

colinator: I've got one of these! Mine is called 'roboflex' (github.com/flexrobotics). It's c++/python, not rust. But similarly born out of frustration with ros. Writing your own robotics middleware seems to be a rite of passage. Just like 'writing your own game engine'. Nothing wrong with that - ros is powerful but has legit problems, and we need alternatives.Although tbh, these days I'm questioning the utility. If I'm the one writing the robot code, then I care a lot about the ergonomics of the libraries or frameworks. But if LLMs are writing it, do I really care? That's a genuine, not rhetorical question. I suppose ergonomics still matter (and maybe matter even more) if I'm the one that has to check all the LLM code....

094459: This doesnt look open source, so maybe not a good comparison with ROS