It really depends. And I say this as someone who’s spent years in the enterprise software management space.
In the last few years, older software has become less capable of running on Windows. Tried to run a 2006 app the other day and it won’t even install. So had to run it in a VM of Windows 7.
Why do you need to run 10-30 year old software? This is a big red flag in my book: if your software can’t be bothered to be upgraded then why would you expect your OS to be?
What is the problem of running 10-30 year old desktop software locally? This is actually very common in some sectors, such as governmental infrastructure or industrial use. It’s not like those applications are reachable from the internet.
Then run it on the relevant (outdated) OS? Why should the OS be constantly held back because the software sucks?
If the developer would just address the issues as they come and recompile for OS upgrades it shouldn’t be a problem — but if you’re using software where the developer can’t bother to recompile after 30(!!!) years I think there’s a more serious problem.
Sometimes software is just… Done. Feature complete and sometimes still just the best way of doing something. It’s a rare thing, but sometimes happens.
I guess a good example is WordPerfect 6.2 for DOS; it’s to this day a great WYSIWYG word processor, and the most feature complete TUI word processor for people who like distraction free writing, and there are still proponents meticulously documenting how to get it working and integrated with modern OS’s so that it can access modern printers.
blackbeans@lemmy.zip 1 day ago
Not sure what you mean by old.
10 year old Windows software? Will definitely run.
20 year old Windows software? Will run but might require admin rights or compatibility mode.
30 year old Windows oftware? Might run but probably need a VM.
For Linux the focus is more on improvement, less on compatibility. That’s a deliberate decision.
Onomatopoeia@lemmy.cafe 1 day ago
Not true.
It really depends. And I say this as someone who’s spent years in the enterprise software management space.
In the last few years, older software has become less capable of running on Windows. Tried to run a 2006 app the other day and it won’t even install. So had to run it in a VM of Windows 7.
blackbeans@lemmy.zip 1 day ago
What is the application you had issues with?
undefined@lemmy.hogru.ch 1 day ago
Why do you need to run 10-30 year old software? This is a big red flag in my book: if your software can’t be bothered to be upgraded then why would you expect your OS to be?
Valmond@lemmy.dbzer0.com 1 day ago
Games comes to mind.
blackbeans@lemmy.zip 1 day ago
What is the problem of running 10-30 year old desktop software locally? This is actually very common in some sectors, such as governmental infrastructure or industrial use. It’s not like those applications are reachable from the internet.
undefined@lemmy.hogru.ch 1 day ago
Then run it on the relevant (outdated) OS? Why should the OS be constantly held back because the software sucks?
If the developer would just address the issues as they come and recompile for OS upgrades it shouldn’t be a problem — but if you’re using software where the developer can’t bother to recompile after 30(!!!) years I think there’s a more serious problem.
ProdigalFrog@slrpnk.net 22 hours ago
Sometimes software is just… Done. Feature complete and sometimes still just the best way of doing something. It’s a rare thing, but sometimes happens.
I guess a good example is WordPerfect 6.2 for DOS; it’s to this day a great WYSIWYG word processor, and the most feature complete TUI word processor for people who like distraction free writing, and there are still proponents meticulously documenting how to get it working and integrated with modern OS’s so that it can access modern printers.