Yes. What’s also true is that sometimes they must be. You will disagree until you find the exception.
There’s nothing great about companies dropping support and also keeping the code in-house so we can’t contract out improvements and fixes, but unless we change that we’re stuck in a world where ridiculously expensive hardware either needs an old OS or becomes astoundingly expensive e-waste. And yes, it needs to connect sometimes. And yes, that’s a scary as shit.
Yes. What’s also true is that sometimes they must be. You will disagree until you find the exception.
No, there should never be any reason to connect these versions to the internet.
If you are talking about legacy software in a corporate setting, then a vm should do the trick 99% of the time. If that legacy software needs an internet connection (which is already questionable), then you bridge only the specific port it needs to the connected interface. If that doesn’t work either, then you get a separate PC explicitly for that software and disallow pretty much all other connections.
If you are talking about private use, then the only thing keeping you on a windows version older than 10 is your unwillingness to upgrade. Its understandable, but it doesn’t change the fact that these versions have massive security holes and shouldn’t be used anymore.
Those versions of windows haven’t had support for years. They shouldn’t even be connected to the internet.
Half od my customers still use Win 7, a few on XP, some on8 for some reason, most on 10.
Then there’s maybe 10% on linux.
Most industries are adverse to change and if you can just patch and continue then fine, especially if you don’t need internet like with a POS.
If you don’t need the internet then why would you care about not having the latest Firefox?
It’s fine to use old unsupported OSes as long as they’re isolated from other machines and cannot access the outside world (and you’re careful).
But nobody should be unironically using Firefox on windows 7. Windows 7 has been EOL for over half a decade at this point.
Yes. What’s also true is that sometimes they must be. You will disagree until you find the exception.
There’s nothing great about companies dropping support and also keeping the code in-house so we can’t contract out improvements and fixes, but unless we change that we’re stuck in a world where ridiculously expensive hardware either needs an old OS or becomes astoundingly expensive e-waste. And yes, it needs to connect sometimes. And yes, that’s a scary as shit.
No, there should never be any reason to connect these versions to the internet.
If you are talking about legacy software in a corporate setting, then a vm should do the trick 99% of the time. If that legacy software needs an internet connection (which is already questionable), then you bridge only the specific port it needs to the connected interface. If that doesn’t work either, then you get a separate PC explicitly for that software and disallow pretty much all other connections.
If you are talking about private use, then the only thing keeping you on a windows version older than 10 is your unwillingness to upgrade. Its understandable, but it doesn’t change the fact that these versions have massive security holes and shouldn’t be used anymore.
Welcome… to the real world.