Live data from Hacker News

My long goodbye to Windows XP (2022)

woodfromeden.substack.com

181–190 of 323 posts

Re: My long goodbye to Windows XP (2022)

#181
post #57

This is not a sensible or technically sound thing to do. It is purely irrational. Win7 is already stuck on Chrome 110/111(?). You are not gaining much by doing this, and are assuming significant risk. Even if specific portions can be quantified away, it's the unknown unknowns that should scare you. Try a Linux distro again maybe? With some non-default themes and Wine, it really should make a better WinXP than WinXP.…

This is a perfect example of modern day superstitions, in no way different from superstitions of stereotypical hairy cavemen sitting around the fire. You react to a program release that is mere three months old with a perfectly capable layout engine that has gathered enormous amount of functionality over who knows how many man-centuries across itself and its library dependencies as if you were told to drive an ox-car…

Sure. Have fun : https://www.opencve.io/cve?product=chrome&vendor=google

Re: My long goodbye to Windows XP (2022)

#183
post #102

Earlier quoted context omitted.

Won't a modern version of Chromium build for XP, with some tweaking?

From my experience, there is a lot of software that will not build for platform older than 7/2008 due to missing APIs. Visual studio stopped support for xp compilation awhile ago. You still can use clang or such for simple programs today, but chromium is probably too complicated to port at this point.

I thought I saw it in Visual Studio 2019 but I'm misremembering - Visual Studio 2017 was the last to support building for Windows XP by the looks of it.

Re: My long goodbye to Windows XP (2022)

#184
post #43

I actually RTFA and was thinking, "this dude should upgrade and run Win7 like me," - and was pleasantly surprised to find he is. The only issue I've had was a few months ago Google Chrome now gives a small nag-bar on startup - supposedly dismissisable with a -flag, but the flag itself is either no longer functioning for some smirk sanctimonious reason, or more likely, hilariously not tested, and has since ironically…

That was the era when my systems felt “most stable.”

Ok, I was also slipstreaming my installation CD-Rs and really putting time into it. Yet. The things that used the most memory and power were probably flash player and counterstrike. Those were not bad times!

I seriously never got malware, and always wondered what everyone else was doing differently than I.

Re: My long goodbye to Windows XP (2022)

#185
post #35

Earlier quoted context omitted.

95 was trash, 98 was gold. XP was great, Vista was trash. 7 was great, 8 was trash. 10 was gold, 11 is trash. Seems Microsoft has to squeeze in at least one bad version between good ones. But never has a new Windows version been made available where people didn't initially hate them at first, XP, 7, and 10 included. It's not until the version after gets released when people really start appreciating what once was.

>11 is trash. 11 has all the same problems 10 has, but brings many significant improvements both in the backend and frontend. Hardly trash. >never has a new Windows version been made available where people didn't initially hate them at first Windows 95 and 98 were both received to applause and fanfare, 95's stellar reception in particular is probably still unmatched to this day.

Windows 11 cranked up the [user-unwanted] telemetry, mandated TPM 2.0, and eliminated hardware support for certain CPU's for no other reason than 'because security' (overridable with a registry hack at least for the moment).

Re: My long goodbye to Windows XP (2022)

#187
post #181

Earlier quoted context omitted.

This is a perfect example of modern day superstitions, in no way different from superstitions of stereotypical hairy cavemen sitting around the fire. You react to a program release that is mere three months old with a perfectly capable layout engine that has gathered enormous amount of functionality over who knows how many man-centuries across itself and its library dependencies as if you were told to drive an ox-car…

Sure. Have fun : https://www.opencve.io/cve?product=chrome&vendor=google

I honestly have no idea whether you are supporting what was said with that link, or objecting to it.

Anyway, I was talking about being inquiring. When you look at that list, surely, some questions do rise. “Why should I worry about all of that to read three paragraphs of text on some webpage?” “Which actions have made it so?” “What should be done to fix it?” Right?

Re: My long goodbye to Windows XP (2022)

#188
The actors attacking old software, are mostly state actors preparing industrial sabotage for cyber warfare. Most xp instances are some industrial equipment with old pcs as controll equipment.

For malware developers those old boxes are uninteresting. To slow, to few, not worth the effort. They are the sloths of the predator and prey ecosystem of software security.

Re: My long goodbye to Windows XP (2022)

#189
post #57

This is not a sensible or technically sound thing to do. It is purely irrational. Win7 is already stuck on Chrome 110/111(?). You are not gaining much by doing this, and are assuming significant risk. Even if specific portions can be quantified away, it's the unknown unknowns that should scare you. Try a Linux distro again maybe? With some non-default themes and Wine, it really should make a better WinXP than WinXP.…

Linux Mint + non networked VM with winXP..

Re: My long goodbye to Windows XP (2022)

#190

Many times have I lost hours, days, or functionality that was never regained to an update/"upgrade." Never have I had my personal computer owned by some exploit that resulted in data loss/breach. Thus, undesired upgrades are a greater risk for personal computing than security. Simple as.

Really? Isn't that a thing of the past? In the last 10 years all my updates on Mac and Windows alike have been a matter of clicking OK and waiting 30-60 minutes. On Linux and BSD I've had some more issues at times but that's been more because of my own messing around.

In Ubuntu, there is a setting to have all security updates happen automatically every day in the background without ever having to bother the user. And its been that way for over a decade. You don't have to be alerted, wait, and restart your whole computer for every little thing. I'm surprised how Mac/Windows still never bothered to catch up. The user should not be bothered by trivial maintenance tasks that the OS should handle.

Hell, I'd do this for all updates if Firefox didn't require an immediate browser restart every time its upgraded.

Post reply on HN