3 ms·
Ok, I've been 10 years in it as well, if that's important. There's simply no reason to skip ROS as a student. My advice was not for businesses, whatsoever. And
by jvanderbot 2y ago
Ok, I've been 10 years in it as well, if that's important.
There's simply no reason to skip ROS as a student. My advice was not for businesses, whatsoever. And every single ROS replacement I've seen is ROS-like enough that the language ROS defined for all of us is effectively lingua franca.
But the antibodies that are triggered by even mentioning ROS should tell anyone how much it is not a fun thing to learn or work with. But it is a common touchpoint. It's really hard to understand _nearly any_ design decision in robotics software without first understanding why it isn't ROS.
- snovv_crash 2y agoI'd rather take a student who put the same effort into building stuff with OpenCV, Eigen or Simulink though. ROS teaches a bunch of bad architecture habits that need to be unlearned, and which many fail to unlearn. People can understand it's bad but then they still build a framework and a distributed system full of async calls to try to replace it, for example.