I am calling bullshit on "outdated software" and going with "checkbox quota diversity hiring".
The airline industry has always had a problem with being behind the times. Air Traffic Control systems, as late as the late 2000s (and probably still does) ran on an implementation of ALGOL-58 called Jovial. That's 1958 in case you were wondering...
Airlines were notorious for running their ticketing and schedule system backends on antique mainframes.
I am not doubting that. In my travels as doing PCI and HIPPA audits I have seen some OLD shit. Not as old as ALGOL but COBOL-68 and FORTRAN systems transacting credit card purchases. For the Java tards out there, every bank and insurance company in the western world uses COBOL backend mainframes. Current actuary software might have some PCP front end but it still has IBM transaction processors in the backend that has been in use since at least 1973. If it ain't broke don't fix it, which (steering back to the topic at hand) is the reason I am calling bullshit on these "technical debt" nonsense.
Mainframes are inherently broken. I'm well aware that they work and are actually quite efficient, however they carry limitations that would end them at any company not run by retarded boomers:
1) They're monolithic systems, which makes it severely problematic to split off or upgrade portions of them. Which is a huge problem for 24/7 operations and technical debt.
2) Batch-based processing is very efficient, and a complete shitshow once job sizes exceed normal volume because there's no quick or reasonable way to scale up capacity. Exhibit A: the Southwest disaster.
3) Incapable of Active-Active High Availability. Mainframes require someone to declare a disaster (which boomers are too scared to do because their shitty ancient systems dont reliably come up from a standby data center). You cant simulate real world problems by randomly yanking cables or shutting down processes Chaos Monkey style without the shitty old mainframes falling over like a boomer with myocarditis.
4) About as dynamic as the tax code. Great if you can manually or batch import all your schedules months in advance, but if it falls over you have no sane way to get schedules running again today. VS a more modern system like Uber where "where are our drivers and vehicles so we can get trips scheduled and seats filled" would be relatively straightforward after an outage.
I can see that, the systems have been running for decades without issue. It's probably a combination of all the above, niggers that don't understand that the old stuff can't be forced.
(post is archived)