On a semi-related note: what's with replacing nginx with their own http daemon? Is the NIH syndrome spreading to OpenBSD as well?
The rate limiting step of the Airway Traffic Control system just might be somewhere else so there would be no need to do anything else.
Just off the top of my head, major limiting factors are runways to get the flights into and out of the air, passenger demand, and the number of air traffic controllers. And like most projects, the cost and effort to scale rises dramatically with the amount of scale you target. Besides, if the system is anything like the air traffic management system I worked on, then it should scale much better than the system it replaced.
I do find it concerning that the system comprises of 'two million lines of code'.
The software on the plane has more lines of code than that and some of that code actually controls the plane, auto-negotiate collision avoidance, etc. I'd be more worried about that - if ERAM goes down for a brief period, controllers wouldn't be able to see flights, but those aircraft would be able to maintain control of their aircraft until ERAM came back up. If the flight's control system went, then the traffic controller would only be able to watch the flight as it hurtled out of control.
And so on. The moment there's not a Next Big Thing You Have to Have, the whole industry goes belly up.
Actually, at that point the only thing left that they can improve would be the quality of the actual content. So yeah, they may very well go belly up.
The shared library is an out of date concept
No, it is used by every major system today for very good reasons.
Some will say that is how Macs do it
Macs do have shared libraries - the files have a
sounds good when storage was expensive
Statically linked apps don't just take up orders of magnitude more storage, but also significantly more memory. Not only that, but a critical security update to one library requires recompiling and redeploying ALL of the apps that use that library.
today we are virtualizing full platforms just to prevent version incomparably
There are tons of reasons to virtualize that have nothing to do with version compatibility or network security.
Since you seem so committed to statically linking apps, I suggest you go through the Linux From Scratch project and statically compile everything. Then, deploy it to an enterprise environment that requires five-nines uptime as well as all security updates. Be sure to set up a video camera so that I can watch with a bug bucket of popcorn.