4 ms·
Just yesterday we had the 30th birthday of Windows NT and while I'm not suggesting that moving between versions would not have required effort, that it probably
by mrweasel 3y ago
Just yesterday we had the 30th birthday of Windows NT and while I'm not suggesting that moving between versions would not have required effort, that it probably the platform you should have opted for if you want multi-decade stability for your application.
You would have need to adapt your code along the way but if you wrote a C++ application or service 30 years ago, there is a good chance of making that run on modern Windows as well.
I'm not a Windows, nor a C++ guy, but that seems like it would have been a pretty safe choice if you built an application back then with the expectation of having it running 50 years later.
- justinclift 3y agoFor long term stuff, maybe mainframes or VMS is where it's at? https://vmssoftware.com https://vmssoftware.com <-- seems to be the company doing VMS these days
- Dalewyn 3y agoWindows and Microsoft are worth respecting for ensuring ancient code will run so long as it follows either of two requirements: Code according to documented standards of the time, or become significant enough that Microsoft will write special patches for you (eg: SimCity). Windows is a really interesting stark contrast to the rest of the computing world that prefers moving fast and breaking things, much to the chagrin of most users.
- pjmlp 3y agoNot the rest of the industry, the mainframe and micro computer worlds are even more focused on that regard. Probably many of Burroughs B5000 applications will still mostly run without any issues on a recent Unisys ClearPath MCP, just as one possible example.