This is all just another example software devs' parochial belief that because software is eating the world, any problem in software is terrible, while ignoring the whole stack of hardware in meatspace that supports the software in the first place.

Like the whole 'internet-connected-cars' panic that occasionally grips developers. You know what's more dangerous than putting a car on the internet? putting a car on the road. There are other drivers out there who could kill you. Thousands of people actually die in accidents. And you want to worry about the infotainment system containing a remote execution vulnerability?

I think it's not that software devs don't care about hardware/meatspace issues, they're just not as well qualified to evaluate them. So they tend to focus on what they know. It's not bad to do that - you can't focus on everything.

Also, wouldn't your argument equally imply that mechanical engineers should drop their parochial belief that hardware issues are terrible while ignoring software problems? (Presuming they do that, which seems not unlikely)