It's not about being internet connected, the point you seem to consistently miss or ignore on purpose and that I already commented on. Learn to read before you start flailing nonsense at keyboard, I wrote ONLY about software stack problems.

It's about having software stack to continue developing without wasting time keeping some legacy crap just so you can compile a code change. But I already wrote it in previous comment. I wrote nothing about internet connectivity aside from criticizing people like you that use it as a logic-bankrupt argument to excuse shit software stack

> I mean, I dunno what else that snark was supposed to mean, but I can assure you that factories don't let their equipment talk to the internet. Anything that the equipment needs will get shipped out to the deployment.

Multiple failures of people accessing SCADA enabled unsecured control systems over internet prove your baseless assumptions wrong.

>You aren't working in this field, that much is clear.

You seem like a guy that needs 6 followups to explain to him how to set up electronic torque wrench then still breaks the bolt so I'm glad I'm not.

And for technician to be able to do that you need someone that develops the fixes anyway, and it's far cheaper in the long term if you don't need to get the software versions from 10 years ago just to run a compile...