3 ms·
I only scanned the article so perhaps I missed it but I can't see any mention of build processes and platforms to run the built artefacts on. My experience of
by kwhitefoot 8y ago
I only scanned the article so perhaps I missed it but I can't see any mention of build processes and platforms to run the built artefacts on.
My experience of software development is that just having the source is close to worthless unless you also have some way of building and running it.
For instance I just downloaded Microsoft's WCF samples. Even with the instructions I am unable to use them because the instructions do not apply to the platform I am using (Win10 Home). If something current from a major supplier that is, presumably, interested in making it work doesn't go then what hope is there for something decades old that runs on an OS and hardware that no longer exists?
- stcredzero 8y agoMy experience of software development is that just having the source is close to worthless unless you also have some way of building and running it. Many old languages could be preserved by implementing AST based interpreters, even non-dynamic languages. Better than having the source and building and running it, is the ability to powerfully debug, monkey patch, and query the runtime.
- tjr 8y agoI work in aerospace. We have a large group of people dedicated to archiving software. When we send them something to archive, we need to provide not only the software itself, but also provide (or provide a link to a previous archive of) all related libraries, build tools, compilers, operating systems, etc. The idea is that absolutely anything could be rebuilt, if needed. Not sure what they do for old development hardware! An interesting question, if you can't run Windows 3.1 on the latest Dell, or whatever. (Or... VMS...) Virtual hardware, perhaps?
- _trampeltier 8y agoJust run the old OS in a VM. But that's usually not the real problem. Often there are some old special hardware interface cards somewhere inside from the old machines.