I do not know how much you know, but I was an Aircraft Mechanic in the Air Force for over 5 years, working on AWACS and KC-135s, so you could say I have some specific knowledge on aircraft engines. There is plenty a pilot could do, as well as the mechanic, but that doesn't make the engines faulty, which was the point. Way to focus on the wrong thing. And just so you know, I have seen over 20 different aircraft with bird strikes in the engine, and nothing flew out of the "tailpipe" but blood and guts. And if you want to get really technical, nothing at all flew out of the tailpipe, as most power from an engine come from the bypass air, which does not go down the core. If a bird strike goes down the core of the egine, there are several stages of fan blades, as well as several compression stages. No solid object will make it out of the "tailpipe." When engines fail during bird strikes, it is caused by two different things. First, the fan blades get damaged, and can strike other fan blades in a different stage, which causes all kinds of problems, and the engine is toast. The other thing that can happen is in a strike down the core, one of the internal stage chambers can crack, which causes fuel to escape through the crack, which is what causes the engine to catch fire.
But back to the whole point of the original post, just because something fails over and over again, does not mean it is faulty. You have to look at what is causing those faults. So before blaming Microsoft for a BSOD, and syaing it is because Windows OS is garbage, you should look at what is causign them. Even when Windows Update installs something, and you get a BSOD, it is because there is a conflict with your hardware, or 3rd party software. There is only so much Microsoft can, or even should, do to idiot proof their OS.
Keep Up with TechRepublic