I'll kick things off:
I think any ROS replacement would need to have a good interoperability story with existing ROS nodes, either by speaking DDS or by having a robust ROS bridge. That probably means it needs to use the same basic paradigm of anonymous pub-sub.
If I were actually trying to make a new robotics middleware, I'd probably start by targeting the early stages of the education market, making something that's easy to add to an Arduino or Micropython project and get automatic sensor drivers and basic controls functionality, but initially lean on the ros protocol for communicating with bigger computers.
Thanks!
My background is in robotics with an emphasis on software; graduated into the first of our many once-in-a-lifetime economic meltdowns in 08, so I did software instead of robotics for a bunch of years. Getting my Masters now to try to reorient the career back to robotics; past five years I was working on cloud infrastructure for robotics fleets, now hoping to get into robotic planning and software.
Now's an interesting time to get into it - I suspect there's going to be a lot of innovation in how we approach the problem and how we build these tools still.
I think this is a game changer because now every business using microsoft 365 has access to AI capabilities and can readily integrate it into their existing workflows. This is bad news for google and slack because Microsoft is way ahead of them but will undoubtedly force innovation.
reply