Random thought: If you want code that you know can be run in 100 years, you should target WINE. This is assuming that the code you’re writing is a medium sized

Random thought: If you want code that you know can be run in 100 years, you should target WINE. This is assuming that the code you’re writing is a medium sized project- a small project would be too trivial, a large one (think MySQL or Java) would probably get ported to a future architecture. Native Windows isn’t great, a lot of Windows 95 binaries have issues running on Windows 11. Linux binaries aren’t great either, I don’t trust Linux binaries from 1999 to work perfectly even now. But WINE? There are millions of pieces of Win32 software from 1995-2030+ (at the very least) that define this period in history. This means that even if we all use some weird alien OS or architecture in 100 years, at least it’s probable that there’s a fork of WINE that future-people use to run obsolete Windows software. So yeah, if I was hypothetically writing an emulator which was for (an obscure enough platform that no other emulators would exist in 100 years), and assuming that the emulator would not be getting patched/ported after 100 years, then WINE-Win32 would probably be the platform I’d aim to support for maximum compatibility in the far future.