3 ms·
I've worked with a fair amount of software that's 50 or so years old and is still in daily use. I don't think that the language its in matters a great deal as
by JohnFen 2y ago
I've worked with a fair amount of software that's 50 or so years old and is still in daily use.
I don't think that the language its in matters a great deal as long as its one that has very wide and deep support. In today's languages, that would mean C/C++, Java, COBOL, and a few others that escape me at the moment.
The bigger issue is going to be hardware changes. A lot of the half-century software I've touched was written for mainframes from the '60s and '70s -- and it's still running today only because those mainframes are being emulated on modern hardware.
I think that, generally, the way you build software that will last is just to engage in excellent engineering practices. Document everything well, keep the code simple, don't get cute or clever, don't follow the fashion of the day, use good names for procedures and variables, don't use magic numbers, and so forth.
- dave4420 2y agoI’d add Javascript and maybe Erlang to that list. (I say maybe for Erlang because I don’t have firsthand experience of it, but I get the impression that they don’t make breaking changes and won’t go away.) I’m tempted to add Go to that list, but it feels premature.
- fizzynut 2y agoI'm curious why you think Javascript should be on the list, I see a lot of issues: Javascript generally runs on a website in a browser: The browser must be continually updated on the client side every few weeks at the very least. Your software must work on all future browsers in 50 years time. Security patches/privacy/laws/etc deprecate/change API calls regularly. The website must continually update certificates, maintain payments to providers / keep valid credentials / not get hacked for 50 years. Most javascript applications have a billion dependencies, and people rewrite using a new framework over updating if it's been a few years, never mind decades. Keeping dependencies up to date for 50 years is a lot of work. I don't know of any instances of anything javascript that has run continually for 20 years to date?
- EuAndreh 2y agoI disagree based on the existence of a standartized but diverse ecosystem. The languages listed above all have: - a language specification; - more than one competing implementation. Erlang doesn't have a specification, so you're actually writing code that runs on the maintained implementation of the VM. This effectivelly ties yours software to the lifecycle of the VM implementation, unlike a situation where diverse implementations and platforms that can execute some code. JavaScript does have a spec, and it does have competing implementations. So if you're to restrict yourself to no dependencies, a standalone webapp could be added. But not for JavaScript outside the browser: there have been efforts to make a coherent interface to the OS, but none stuck. So now you need to pick a platform to restrict yourself to. --- I've explicitly highlighted the lack of dependencies with JavaScript just because how pathological this ecosystem is in this aspect. It doesn't have to be zero, and it does apply to other languages and ecosystems, but "a simple react app" absolutely fails this rule.