> How low has the SW development bar gone, if "it's okay" now means "at least it's not directly killing people"?

I though that was the way ever since OS/2 failed. Getting stuff out to customers has priority over quality control.

There has always been a tradeoff between reliability and development time. There wouldn't be a games industry if every video game had the same level of software assurance as a mars lander, because Tetris would cost $200m to develop. A medical simulator lies somewhere between a mars lander and a video game - it needs to provide accurate simulation, but the odd crash isn't a complete dealbreaker.

The bug is now patched, so the downtime appears to be less than 24 hours from discovery to fix. The original error is clearly a major blunder, but Oculus have responded properly.

>How low has the SW development bar gone, if "it's okay" now means "at least it's not directly killing people"?

It gets that low every time a hospital underfunds IT staff and makes horrible project management decisions and product buying decisions.

I've seen that first hand. There's a bunch of corpses at the IT entrance of people who've tried to turn that around.

The GP was suggesting that this could kill people. I simply implied that it wouldn't, and compared to killing people, I would say a lost day is "okay".