5 ms·
https://web.archive.org/web/20010726224437if_/http://www.textfiles.com:80/groups/CDC https://web.archive.org/web/20010726224437if_/http://www.tex... https://ww
by 1vuio0pswjnm7 3y ago
https://web.archive.org/web/20010726224437if_/http://www.textfiles.com:80/groups/CDC https://web.archive.org/web/20010726224437if_/http://www.tex...
https://www.reuters.com/investigates/special-report/usa-politics-beto-orourke/ https://www.reuters.com/investigates/special-report/usa-poli...
Some years ago I was going through some old laptops, older than many HN readers and commenters no doubt, and these were loaded with old versions of Windows. I decided to see if I could use one by remotely controlling it from a more powerful computer running UNIX-like OS over the local network. It seemed all the popular "remote desktop" software used to do this with these old versions of Windows is long forgotten and difficult to find. "Unsupported", "deprecated", not "modern", yada, yada. So I got a copy of Back Orifice, which is still easy to find, and it worked like a charm. Small, easy to use. Does what it's supposed to do and not much else.
This reminded me just how bad software today has become, even worse than it was, and how Microsoft and its partners rely on planned obsolesence and turn perfectly usable computers into e-waste. Windows XP, everyone must stop using it offline because MS wants it to disappear. (As if Microsoft can control what software people choose to run on their computers.) Connect to the internet 24/7 and use "Windows 11" instead. Don't worry, MS has got people covered with its "automatic updates". Command and control from Redmond.
This is why I use NetBSD and Linux distributions. The latest release runs fine on all those old laptops. That's what "backwards compatibility" means to me.
- jmspring 3y ago"Planned obsolesence"... I get the desire to bash Microsoft at every possible opportunity here, but one thing Microsoft did better than most companies was backward compatibility and the ability to run legacy programs / maintain API compatibility going back years. Windows 3.x -> 95/98 legacy (even 16bit) apps continued to work. There are APIs even in Win10/etc that support old apps. I don't think Microsoft can be one of those "orchestrating planned obsolesence". This comment is particularly inaccurate. There are things that are valid for complaining about Microsoft, but "planned obsolesence"? No.
- coldtea 3y agoMaybe not "planned obsolesence", but they do however have a "API incontinence". This is mostly driven from a desire to sell new crap to enterprises. So they rewrite everything and churn out new crap every few years, new APIs, new frameworks, new "this is the way to do X now" and so on. So, them maintaining backwards compatibility for the old stuff is half of the picture. Developers and (especially enteprise customers) are still pushed to adopt some new thing with alarming frequency, and stuff that works perfectly well gets thrown out for the new hotness. This leads to a rat race to keep up with the latest stuff, no updating of old stuff with new functionality, and so on.
- jmspring 3y agoExplain to me how win32 APIs from the 90s were still a thing on win mobile in the mid 2000s? On the enterprise front, yes they probably want to push but you ignore how often there are Windows EOL announcements where things are extended for large "enterprises" including government and large customers.
- coldtea 3y ago>Explain to me how win32 APIs from the 90s were still a thing on win mobile in the mid 2000s? Not sure what you're asking. I didn't say they kill and stop supporting old APIs. I said they keeping putting out and pushing for "new hotness" APIs/frameworks, forgetting their old APIs/frameworks with an alarming rate. A 20 year old API still working is good. A 20 year old API properly maintained and updated, instead of having several new APIs/frameworks introduced and killed in between, with like the 5th "doomed to be replaced soon" API/framework now pushed as "THE" way to do things, is even better.
- jmspring 3y agoPlanned obsolesence was mentioned, legacy APIs being maintained and old programs continuing to run... that's not obsoleting anything.
- mike_hock 3y ago> Microsoft and its partners rely on planned obsolesence and turn perfectly usable computers into e-waste. > This is why I use NetBSD and Linux distributions. The latest release runs fine on all those old laptops. That's what "backwards compatibility" means to me. Based. Yet, I get downvoted when I complain about i686 support being phased out.
- jeroenhd 3y agoI'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.
- 1vuio0pswjnm7 3y agoIt may be that I just don't know enough about the software used to control old versions of Windows from UNIX, and I just found Back Orifice the easiest option. In any event, I appreciate the cDc software. That was the point of the story. I have used their nc for Windows as well, the one written by Weld Pond.
- 1vuio0pswjnm7 3y agoCorrection: Windows nc came from another group, not the cDc.
- fomine3 3y agoRDP is one of a big hole to be used for hacking. I understand why Microsoft want to deprecate older protocols.