[Joel_Mckay]

ROS is dozens of projects crammed into a single workspace. Avoiding this ecosystem will not work in your favor in the long term.

* robotic software projects are often abandoned, and only ROS keeps the driver packages working

* Yes it is terrible, but the alternatives are even worse

Almost all modern reasonably good platforms will already offer a tested ROS configuration. Even the UR5 had simulation and control options out of the box.

People can't avoid standards.. even the awful ones.. =3

[rck]

Yeah, for professional robotics you just accept that this is the world we live in. But for learning and hobbyist stuff, it's better to play with simple hardware and build the things that ROS is ultimately abstracting over before you try to pick up ROS.

I've seen people get sucked into ROS + simulation who end up never touching real robots. Which is fine if that's what you want to play with, but it's debatable if "ROS + sim" alone is even "robotics."

[Joel_Mckay]

I usually recommend building the Arduino turtle-bot first, try the maze solver with the classic wavefront algorithm, and then a ROS Arduino setup tutorial.

Also not a fan of simulators for simple platforms, as a lot of stuff breaks when the environment is chaotic. =3