How would (You) fix this mess?

...

...

to be clear i meant C would have been massively more sane than C++. C isn't a good language but 99% of the faggots who agree are some web shotter faggots

...

Ada was proven to work. Why should they take something that they know works and replace it with something they know is worse? It doesn't make any sense to me. If they wanted to test out a new language like Rust or Go and it was worse, that's one thing, but they know C++ sucks. Everyone knows C++ sucks.

This is the UNIX "it doesn't matter" mantra all over again. "Doesn't matter" always means "sucks". When someone selling a car says "gas mileage doesn't matter" they're saying "the car's gas mileage sucks." Programming languages matter. If someone trying to get you to use a programming language says it doesn't matter, the language sucks.

C++ is worse than Ada, but it's also worse than the languages that were previously used in flight software. If the programmers aren't smart enough or just don't care enough to learn Ada, Fortran, Cobol, or whatever, they shouldn't be working on this sort of thing anyway.

Are the memory devices too slow or does the software just suck? If they're using XML or some UNIX-inspired text bullshit, their memory won't go as far.

Why am I retraining myself in Ada? Because since 1979 Ihave been trying to write reliable code in C. (Definition:reliable code never gives wrong answers without an explicitapology.) Trying and failing. I have been frustrated tothe screaming point by trying to write code that couldsurvive (some) run-time errors in other people's code linkedwith it. I'd look wistfully at BSD's three-argument signalhandlers, which at least offered the possibility of providehardware specific recovery code in #ifdefs, but grit myteeth and struggle on having to write code that would workin System V as well.There are times when I feel that clocks are running fasterbut the calendar is running backwards. My first seriousprogramming was done in Burroughs B6700 Extended Algol. Igot used to the idea that if the hardware can't give you theright answer, it complains, and your ON OVERFLOW statementhas a chance to do something else. That saved my bacon morethan once.When I met C, it was obviously pathetic compared with the_real_ languages I'd used, but heck, it ran on a 16-bitmachine, and it was better than 'as'. When the VAX cameout, I was very pleased: "the interrupt on integer overflowbit is _just_ what I want". Then I was very disappointed:"the wretched C system _has_ a signal for integer overflowbut makes sure it never happens even when it ought to".It would be a good thing if hardware designers wouldremember that the ANSI C standard provides _two_ forms of"integer" arithmetic: 'unsigned' arithmetic which must wraparound, and 'signed' arithmetic which MAY TRAP (or wrap, ormake demons fly out of your nose). "Portable Cprogrammers", know that they CANNOT rely on integerarithmetic _not_ trapping, and they know (if they have donetheir homework) that there are commercially significantmachines where C integer overflow _is_ trapped, so theywould rather the Alpha trapped so that they could use theAlpha as a porting base.

you'd be hardpressed to find enough engineers for it whereas there are plenty of professional pajeets that can code in c++

By not getting rid of reliable software that works by replacing it with unstable software with a billion useless features and then paying some contractors millions of dollars to ll contractors to make it.
My mother is a fed and they are doing this at her work, and they wonder why they are over budget. They literally dumb down the software she has to use so it can be ran on a smart phone. Why would you want to do that? The team behind are so soykaf that they can't even sort records in a way that's not alphabetical or numerical. I could implement that in less that 5 minutes. In fact, I could probably make the whole piece of software myself both faster and cheaper.
It infuriates me whenever my mom talks about about the technology at her work because they keep making terrible decisions.

1. Remove the government
2. rewrite everything in haskell

...

While it's a government contract that, therefore, does not have professional pajeets, all of the engineers aspire to be professional pajeets. By using sepples, the contractors are growing job skills using a language that is prevalent in industry. Of course, it is prevalent in industry because companies want to use a language that makes their local programmers fungible with pajeets, as pajeets are cheaper. The contractors view using sepples as career growth. There is also the ability to use sexy new technology: many open source projects use C or sepples, and using sepples makes integrating those projects into the code easier. Why should government contractors rewrite X in Ada, when X is an open-source C project? Who is going to maintain that Ada version? What do you do when the engineers who wrote it retire and no one knows how the code works?