In software, "stable" often means that, given certain assumptions (OS interfaces, working hardware, etc), the code will not crash even if given bad inputs. Bas

In software, "stable" often means that, given certain assumptions (OS interfaces, working hardware, etc), the code will not crash even if given bad inputs. Based on my reading of this thread, in aviation, "stable" means that, given certain assumptions (fuel supply, etc), the plane will tend to return to equilibrium after pretensions along one particular axis, if you give it no inputs. Pilots in the thread, please correct me if I'm wrong. You may think to yourself "that's stupid, stable means it doesn't crash!" But if you want to communicate with people in the field, you have to learn their language. If an astrophysicist said "what do you mean that program is stable?? It doesn't have enough hydrogen to roast a marshmallow, much less initiate and sustain fusion!" you would roll your eyes. Sure it's all the same English word, and there is even a common semantic root, but they all mean very different things in their contexts.