News for hackers. Stuff that matters.
Re:A Tragic Loss by thaumasiotes on Thursday June 30, 2016 @07:32PM (#12012713)
On the contrary, every plane that takes off does so despite the known chance that it could crash.
Re:A Tragic Loss by jsprogrammer on Thursday June 30, 2016 @08:00PM (#12012882)
No. I am talking about calculated chances, not "someone might decide to crash the plane" chances. If there is a known chance that a component of a plane might fail and cause a crash, it will not take off.
Re:A Tragic Loss by YeGoblynQueenne on Thursday June 30, 2016 @08:04PM (#12012910)
>> If there is a known chance that a component of a plane might fail and cause a crash, it will not take off.

There is no component of any machine that is 100% guaranteed to not fail under any circumstances. What the bloody hell are you talking about?

Re:A Tragic Loss by jsprogrammer on Thursday June 30, 2016 @08:18PM (#12012966)
Known, calculable circumstances. If a component may fail, then redundancies are added so that failure will not result in a crash.
Re:A Tragic Loss by YeGoblynQueenne on Thursday June 30, 2016 @08:38PM (#12013034)
"Redundancies are added"? Sorry but you just made that up. If the risk of an accident and death was "calculable" in the way you're trying to say it is, we wouldn't "add redundancies". We'd just avoid flying (or driving) and nobody would ever die in an accident.
Re:A Tragic Loss by thaumasiotes on Thursday June 30, 2016 @08:33PM (#12013019)
You just keep digging. All adding redundancy can do is lower the chance of a crash.

> If a component may fail

As has already been pointed out to you, all components may fail, including any that you add to compensate for the potential failure of other components.

An engineer should know this by instinct.

Re:A Tragic Loss by jsprogrammer on Thursday June 30, 2016 @11:01PM (#12013625)
An engineer should know nothing by instinct.

Adding redundancy was incorrect. Redundancy should be inherent to the design. If one must be added, the design is already a failure.

Redundancy does not mean adding a new component, but maintaining operation under component failure. For example, if the engines fail, it should still be possible to make a controlled landing.

Re:A Tragic Loss by mthoms on Friday July 01, 2016 @12:33AM (#12013891)
If you can build an airliner with 100% failsafe redundancies at a cost that makes you competitive with the incumbants I'll be the first to buy a ticket. Heck, I'll be the first to invest.
Re:A Tragic Loss by jsprogrammer on Friday July 01, 2016 @01:08AM (#12013997)
Nothing is 100% failsafe. Machines can be designed that will not enter known failure modes, given they are operating in within known conditions. If such a machine is detected to be able to enter a failure mode in expected coming conditions, it should not be used commercially.

Cf. The grounding of all Boeing 787s: https://en.m.wikipedia.org/wiki/Boeing_787_Dreamliner_batter...

Re:A Tragic Loss by jfrisby on Thursday June 30, 2016 @08:07PM (#12012923)
Wrong.

One in 1.2 million flights crash. This is literally a "known chance".

Planes take off anyway.

Re:A Tragic Loss by jsprogrammer on Thursday June 30, 2016 @11:38PM (#12013722)
No, that is an observed statistic.
Re:A Tragic Loss by jfrisby on Friday July 01, 2016 @05:23PM (#12019754)
And the difference is?
Re:A Tragic Loss by jsprogrammer on Saturday July 02, 2016 @02:24PM (#12023368)
One is predictive, the other is retrospective.
Re:A Tragic Loss by jfrisby on Saturday July 02, 2016 @06:26PM (#12023993)
Except that the retrospective IS predictive.
Re:A Tragic Loss by jsprogrammer on Saturday July 02, 2016 @06:48PM (#12024059)
What evidence supports that position?

Crashes are anaomolus events that happen for very specific reasons. Reasons that do not have any seeming connection to any other crash. I don't see how a retrospective could predict anything about the success of future flights.

Re:A Tragic Loss by jfrisby on Monday July 04, 2016 @12:59AM (#12028955)