2 ms·
I'm pretty sure the latest VNC clients can still connect to VNC servers from the XP era. How unsupported XP really is depends on the programs you try to run on
by jeroenhd 3y ago
I'm pretty sure the latest VNC clients can still connect to VNC servers from the XP era. How unsupported XP really is depends on the programs you try to run on it.
XP works fine (though it's insecure and a reminder about that is not bad) but that doesn't mean every piece of software has to support it. Hardware acceleration and usable 64 bit software has made a major difference in making animations and transitions possible. Clunky or simply bad kernel APIs were replaced with better ones.
All the old APIs are still available, but nobody makes software for a system only retro enthusiasts and some old factory control units are using. There's no interest in keeping it work, there are too many workarounds necessary, and nobody is willing to pay anyone for XP support.
Don't think Linux is much better. Getting code from 2004 to compile can be a real pain because the dependencies of yore have long been discontinued, their tarballs hidden somewhere on archive.org, and its reliance on 32 bit GCC behaviour long broken. Old hardware drivers break all the time because nobody has the hardware or the interest to keep that one Toshiba CD drive you have working on kernel 6.5. If your sound card isn't one that's used in virtual machines, good luck making it work out of the box. Your only advantage is that most Linux software is open source (but far from all of it) so recompiling it for modern systems is possible, but that doesn't mean it's any easier.
Starting with Windows 8, but quickly advancing after the release of Windows 10, the enshittification of Windows is real and it sucks. I'd love the modern Windows kernel running the 7 or XP UI stack instead of whatever the hell Windows 11 is supposed to be. However, programs only supporting the operating systems people use isn't breaking backwards compatibility, it's just good business.