News for hackers. Stuff that matters.
Re:Delta Computer Glitches Force Flight Halts Third Year in ... by danso on Wednesday September 26, 2018 @10:36AM (#18076349)
The end of the article provides this comparison for context:

> Still, Delta isn’t the only U.S. carrier to have suffered from technical glitches. In December 2017, a fire at Atlanta’s airport, the world’s busiest hub, caused a major electrical disruption, crippling services and stranding thousands of passengers of Delta as well as rivals including Southwest Airlines Co.

It seems to me that Southwest's systems being brought down by fire and electrical disruption is a different "technical glitch" than the kind of systems problem Delta just had. A better comparison would be July 2016, when a router failure created a "chokepoint that crippled hundreds of the company's software applications":

https://www.dallasnews.com/business/southwest-airlines/2016/...

Re:Delta Computer Glitches Force Flight Halts Third Year in ... by Twirrim on Wednesday September 26, 2018 @12:26PM (#18077581)
> It seems to me that Southwest's systems being brought down by fire and electrical disruption is a different "technical glitch" than the kind of systems problem Delta just had.

To some degree, sure. But they really should be capable of a straight failover (forced, if necessary) to geographically separate components.

Re:Delta Computer Glitches Force Flight Halts Third Year in ... by txcwpalpha on Wednesday September 26, 2018 @12:40PM (#18077729)
>To some degree, sure. But they really should be capable of a straight failover (forced, if necessary) to geographically separate components.

AFAIK the failure at ATL had nothing to do with the ability for the IT network to failover. It was because the power at the airport was off, and therefor the airport was unable to fly planes. And when the world's largest airport goes dark, it causes ripples in delays across the entire country because of misplaced planes/staff/passengers. And you can't just "failover" hundreds of planes and thousands of passengers to a different geographic location.

We're really talking about two completely different types of failure here, and the other comment is right in that it's weird to compare the ATL fire to last night's failure.

Re:Delta Computer Glitches Force Flight Halts Third Year in ... by AnimalMuppet on Wednesday September 26, 2018 @04:11PM (#18079794)
It's weird to those who know. But to those who are just looking at how bad it messes things up from a passenger's view (ie, non-aviation-knowlegeable people reading the article), it's reasonable to compare things of different causes that have similar effects.
Re:Delta Computer Glitches Force Flight Halts Third Year in ... by txcwpalpha on Wednesday September 26, 2018 @05:17PM (#18080360)
True, but if that's the case then why doesn't the article bring up all of the adverse weather events that have had the same impact?

Even for non-aviation-or-tech-knowledgeable people, I think most still care who is at fault for such disruptions. The article frames the ATL fire as Delta/Southwest's fault. It puts the ATL fire in the same category as other, airline-specific issues that were caused by Delta's IT systems. But that just isn't the case. The ATL fire affected every airline at ATL (but for some reason the article only calls out SW and DL), and was the fault of the airport, not the airlines. It's more similar to bad weather shutting down an airport than it is to the IT issues that Delta faced last night.

It just feels like bad reporting to include that comparison.