You don't have to stop at the gas phase.

https://en.m.wikipedia.org/wiki/Inductively_coupled_plasma#A...

Can confirm. $DAYJOB makes robots subject to hard worst-case latency constraints. The product runs on QNX.

Can confirm https://github.com/jonls/redshift works great; been using it for years.

You treat it like the metaphorical toxic waste it is: avoid it at all costs. You don't need ROS to get a dependency manager, a build system, a middleware, and/or a process manager.

Can confirm. I am a grown man and my professional work with ROS has made me cry.

My colleagues and I used to joke that any build system issue you encounter will be addressed in next year's build system.

* https://wiki.ros.org/rosbuild

* https://wiki.ros.org/catkin

* https://docs.ros.org/en/jazzy/Tutorials/Beginner-Client-Libr...

* https://docs.ros.org/en/jazzy/How-To-Guides/Ament-CMake-Docu...

It doesn't feel like a joke anymore.

You forgot ament.

Whoops, sorry. I must have repressed that trauma.

I have worked in two failed and failing startups that invested heavily in ROS. I could fill several volumes with "ROS Gotchas". Everything in the ROS stack is either a useless curio or an on-fire clown car.

Using ROS is a great way to turn your project and business into a cautionary tale.

Relevant: https://newsboat.org/

If you like your email in mutt, then you'll probably like your feeds in newsboat.

This is not a comment about open/closed-source software and/or licensing models.

Projects like this never fail to impress me vis-a-vis source obfuscation. The 'generate.pyz' is an interesting twist on the usual practice.

    #  You may not reverse engineer, decompile, disassemble, or otherwise attempt
    #  to derive the source code or underlying structure of this script

This prohibition is void in certain relevant jurisdictions, for any publicly available product.