Remix.run Logo
▲ NegativeK a day ago

> At what cost? Some. At some cost.

This doesn't address how the cost of safety related procedures versus the cost of risks mitigated is calculated (which is way harder than saying "some") so that the buyer can actually know what "some" cost is.

It's also not addressing the parent comment's point: the bad outcomes in aviation tend to be very impactful (both in human safety and financially), so the tolerance for mistakes is way lower.

Compared to cybersecurity for a brochureware website, where it takes a far larger stretch to go from "security incident" to "someone's dead". (Also, people in cybersecurity aren't going to accept "it has some cost, and you might buy it if it's not too expensive".)

▲reverius42 21 hours ago | parent [-]

For the commercial flight industry this is very easy to calculate: zero deaths are acceptable. This is not like car manufacturer recall calculations (famously, referenced in Fight Club: if the lawsuit costs the manufacturer less than the recall, they don't recall). The airline industry is built different thanks to heavy regulation.

You could ask: is it _worth_ making it that safe? But we don't ask that. We just make it that safe.

I think there is a good point to be made that this level of safety (it costs what it costs) is probably not worth it for cybersecurity, in general, even if it's largely considered worth it for commercial aviation.

▲disgruntledphd2 16 hours ago | parent [-]

As software intermediates more and more of the physical world, we're gonna end up at least as regulated as finance, and potentially as much as aviation.

The only real question is how much damage will be caused before that happens.