Programming for longevity is probably less about the specific language or tooling choices and more about things like: can you reproduce the build or does it pre

Programming for longevity is probably less about the specific language or tooling choices and more about things like: can you reproduce the build or does it presume a specific environment? How is the source code stored and how can it be recovered if the primary location is lost? Is the system well documented? Are the abstractions robust, and well composed? Many mainframe systems survived while desktop based systems have been killed because of the server/client architecture that has allowed for new front-ends to built separate from the backend. In this sense, if you are building for malleability, things like good test coverage become very important to support refactoring and changes. I'm sure many other considerations apply.