Hacker News Reader

Comment by jl6 | Hacker News Reader

> How does someone write software that needs to run for ~50 years where the hardware will need to be replaced with non-equivalent, newer hardware?

Some ideas:

Write it in a popular language/ecosystem, stick rigidly to well-defined APIs, use commodity hardware, flatten out any malignant cleverness, maintain documentation on why every part does the thing it does, and make the source code readily available.

This is based on working with some very old systems, and each point above is the opposite of something that made life harder.

View on HN

Unfortunately, “popular language/ecosystem” includes JavaScript and PHP.

I’d go for “universal and timeless”, which has meant C for several decades now. There is, I’d concede, a reasonable chance that Rust obtains that label in our lifetimes.

Yeah agreed. Popular is a good first approximation, but to be more precise I think you want tools where the incentives in the community reward stability over features that require breakage, which would include languages and runtimes like Erlang and Clojure.

Neither is popular when compared to for example Python or PHP, but they both have cultures that care about stability in the core runtime and the libraries. Most folks probably don’t know that about Erlang and maybe think it’s some new whiz-bang thing, but Erlang is incredibly stable and well supported by a dedicated team that has been doing it for years and years at this point. I don’t know if Erlang will be more or less popular in 20 years but it 100% will be around and be receiving updates, I would put money on it.

My C programs from a few decades ago, before namespaces were invented, no longer compile. However, the old executables still execute. The old C compilers are available but not supported; ChatGPT warns to expect trouble. Perhaps maybe there are compatibility switches that work correctly. Using them would require changing the makefiles.

And worse for posterity, Python

The Amiga was a popular ecosystem.

And as a result it's very well emulated, making it very likely that Amiga code can still be run in 50 years' time.

Today. That was not true a few years ago.

I remember Amiga emulators (notice the plural) going all the way back to when i was in high school - and that was around 1999-2001 or so.

That was about the time frame of the commercial Windows NT emulator mentioned up thread. There was a market for them.

Today’s landscape is shaped by the pandemic. In between, there were many years of impracticality.

Perl was popular

Reply on news.ycombinator.com