3 ms·

C (C99) and Javascript (ES5) are very likely to still be supported. Most protocols will be phased out for security reasons. So I would go with direct TCP/UDP b

C (C99) and Javascript (ES5) are very likely to still be supported. Most protocols will be phased out for security reasons. So I would go with direct TCP/UDP based on Linux kernel syscall (still the weakest point) in C or with fetch in JS. Most operating systems will be trivially vulnerable to attacks, so I would go with the minimal possible attack surface (hardened kernel, firewalled, etc.) It should survive and TCP/UDP communication makes it easy to integrate with any other software. For the hardware I would go with a Raspberry pi if possible (and in C), otherwise just hosted on AWS. About its usefulness, that would be hardest point. If it was useful and not updated for 5-10 years, it will be replaced however complex it is, 100 years later the problem might be generalized or not relevant anymore. Looking at what's there: - 61 years old, MOCAS, OS written in COBOL used US Department of Defense, on a mainframe - Linux, Python, glibc, perl, emacs, ...: Most old software still relevant is a core foundation (programming languages, operating systems, text editors) - NASA's software: C, C++, Ada, Python. Linux for applications, Windows for end users. So I would probably make a minimal programming language, maybe some kind of minimal Crystal.

shittyadmin 8y ago
> based on Linux kernel syscall (still the weakest point) The Berkley sockets API is pretty well supported on all major operating systems via C libraries with only slight differences and even if it dies out will likely have shims available for a long time to come. Why use a direct syscall interface over this?
gspetr 8y ago
> otherwise just hosted on AWS. Talking about decreasing risk of failure by minimizing attack surface, but at the same time greatly increasing it by maximizing vendor lock-in, essentially betting Amazon will still be around in 100 years, it just does not feel like a very sound strategy.
zelly 8y ago
C, yes. As terrible as C is, I have no doubt that people will be using software written in C everyday in year 2300. > So I would probably make a minimal programming language, maybe some kind of minimal Crystal. A new programming language made now (such as Crystal) has the least likelihood of lasting 100+ years, no matter how good it is.

shittyadmin 8y ago

> based on Linux kernel syscall (still the weakest point) The Berkley sockets API is pretty well supported on all major operating systems via C libraries with only slight differences and even if it dies out will likely have shims available for a long time to come. Why use a direct syscall interface over this?

gspetr 8y ago

> otherwise just hosted on AWS. Talking about decreasing risk of failure by minimizing attack surface, but at the same time greatly increasing it by maximizing vendor lock-in, essentially betting Amazon will still be around in 100 years, it just does not feel like a very sound strategy.

zelly 8y ago

C, yes. As terrible as C is, I have no doubt that people will be using software written in C everyday in year 2300. > So I would probably make a minimal programming language, maybe some kind of minimal Crystal. A new programming language made now (such as Crystal) has the least likelihood of lasting 100+ years, no matter how good it is.