This thread has gotten pretty toxic.
So before it gets closed…
Thanks @Katherine_Scott & everyone who’s at Intrinsic working on ROS, Gazebo & OpenRMF.
Thanks @gbiggs for dealing with the community.
Thanks @facontidavide for all the open source work on BTrees, PlotJuggler etc.
Thanks @smac for Nav 2 work @gavanderhoorn for the work on ROS-I
And @DLu for your work on Nav 1 & the meme that kicked off this conversation…
I’ll try to keep my bias out of this, and note this is my option, and not that of any current or former employers.
But the original meme was calling out a group, inappropriately, and was flagged. 
The edited meme still mentioned a specific product. And was again flagged.
Obviously it’s struck a nerve in the community. The endless memes reminding everyone ROS 1 is coming to an end, showing it in the bottom of the pool…
I’ve used ROS for 14 years, and have been in some way preparing for, or dealing with ROS 2 migrations for almost 7 years, since Bouncy… it’s painful. Much more painful than the wet-dry rosbuild to catkin transition.
But really ROS users can’t expect Willow Garage, Open Robotics and now Intrinsic employees to do majority of the work.
Why is the migration painful?
Because it takes time, and it’s often hard to prioritize. And it gets harder the longer you put it off.
Most of us have been the parent in the pool dealing with some product launch or critical issue, and often under employer contracts that make getting contributions upstream difficult… or working around some upstream bug with a quick fix that’s not easy to generalize and contribute back… and that so many companies built on top of ROS have internally been reinventing wheels.
The reality is just exposing the classic xkcd comic: