this post was submitted on 14 Jul 2023
70 points (100.0% liked)

Programming Humor

2662 readers
2 users here now

Related Communities !programmerhumor@lemmy.ml !programmer_humor@programming.dev !programmerhumor@kbin.social !programming_horror@programming.dev

Other Programming Communities !programming@beehaw.org !programming@programming.dev !programming@lemmy.ml !programming@kbin.social !learn_programming@programming.dev !functional_programming@programming.dev !embedded_prog@lemmy.ml

founded 1 year ago
MODERATORS
top 15 comments
sorted by: hot top controversial new old
[–] LillianVS@lemmy.world 12 points 1 year ago (1 children)

"You have no reason to be scared of flying, they take better care of their planes and have more safety checks than driving a car."

The plane:

[–] DoomBot5@lemmy.world 5 points 1 year ago (1 children)

I'm sure at least 1 bug like this exists in your car.

[–] 567PrimeMover@kbin.social 4 points 1 year ago (2 children)

Wasn't there a car (I think it was a jeep cherokee) a few years ago where the CANBUS could get hacked via bluetooth and they were able to fuck with the brakes?

I also remember a GM scandal maybe a decade or two ago where the key could just fall out of the ignition and kill your car while you were driving

Even farther back there was that cool thing with the ford pinto where the gas tank would explode in a rear end collision and cook you alive

[–] Xeelee@kbin.social 1 points 1 year ago

The US car industry has never been known for being safety conscious.

[–] dismalnow@kbin.social 1 points 1 year ago (1 children)

Feels like someone gives a talk about this every year at defcon.

[–] DoomBot5@lemmy.world 1 points 1 year ago

Pretty sure your ride to defcon is already hacked by the time it drops you off there.

[–] Flexaris@discuss.tchncs.de 5 points 1 year ago (2 children)

Are airplanes really on continiously for 51 days? Sounds pretty impressive to be honest

[–] Nommer@lemmy.world 5 points 1 year ago

Typically yes. Usually for faster turn around times. When they pull into a terminal ground power is attached so they don't need to restart the computers and realign navigation systems during the day. At night when nobody is flying there really isn't a reason to go fully cold.

[–] DoomBot5@lemmy.world 3 points 1 year ago

No reason to turn off the flight computer between flights (until stuff like this gives you a reason).

[–] xoggy@programming.dev 5 points 1 year ago (1 children)
[–] 2e8a9d6bb6935a54@lemmy.world 3 points 1 year ago

One man's pain is another one's comedy :)

[–] Zron@lemmy.world 4 points 1 year ago (3 children)

One of the reason planes and vehicles in general are so reliable and safe is because all of the components are supposed to be rigorously tested until all failure modes can be accounted for and work around a found.

Now Boeing has had some oopsies with their angle of attack indicators back in ~2016, but those were new parts that’s clearly didn’t get tested enough.

This computer is likely an old design and it’s kept that way because we know how it fails, can predict those failures and know how to respond to them. Switching to a newer flight computer with a 64bit architecture would allow for storage of longer numbers, but it would also mean that every line of every bit of software that touches that computer would have to be gone over and tested with a fine toothed comb before any plane with the new computer would be allowed to fly again.

It’s much cheaper and safer to use an already known design and just work within its limits.

[–] azi@mander.xyz 2 points 1 month ago

Depends how hard it is to work within its limits. This bug/hardware limitation creates a point of failure (someone not resetting the computer when they're supposed to)

[–] lemann@lemmy.one 2 points 1 year ago

A part of me just wants to think "Boeing A Big Evil Corpo Trying To Save Costs" ☹️

But then there are genuine cases that flip this thinking on its head, like the ISS and its increased resistance to bit flips from solar flares, partially due to the larger electronics manufacturing techniques at the time it was created (tried to find my source for this but couldn't)

Then you have the ESA sticking with the Arianne 4 codebase because it was "tried and tested" when they built Arianne 5, which led to the first Arianne 5 exploding shortly after liftoff...