> but they lack so much: reliability engineering, failure testing, ruggedness requirements, industry certifications, QA, I could go on.
Sometimes you don't need all that stuff. Sometimes it's as simple as using a neural net to count the number of people in a room at a given time, or get a sensor to publish data online, or provide a networking shim for a RS232 device that fits in a small space.
There are also many use cases where having 10 working backup copies of a $35 device on a shelf that can be swapped in under a minute is a much better reliability guarantee than 1 $2000 industrial certified, QA certified, FDA approved, UL listed, GDPR compliant device whose tech support is in some other timezone, takes holidays, and isn't 24/7.
It's just that the easiest thing that can fail on a raspberry pi in my experience is the stupid micro-B/USB-C connector, so fixing that, which would cost pennies to put a slightly more rugged molex or other connector on the PCB, would be a really nice addition. The rest of the Pi is actually pretty reliable in my experience.
> stopped the production line at 2 a.m.?
Production lines aren't the only use case for Raspberry Pis in industry. Many production lines also don't run at 2am.