Go-legacy-winxp: Compile Golang 1.24 code for Windows XP
github.com116 points by Oxodao 4 days ago
116 points by Oxodao 4 days ago
There's a surprisingly large Windows XP community; everything from security patches to browsers[0] to third party Discord clients[1].
[0] https://www.mypal-browser.org/ [1] https://github.com/DiscordMessenger/dm
What I don't understand is... why? I understand keeping alive software for the sake of hardware compatibility, but browsing the web and running Discord? Is it all really just to save a few hundred dollars over... 24 years?
Perhaps because the level of respect that Windows has for its users has dropped with each successive version?
Not to mention bloat: I have a keyboard with a dedicated calculator button. On a machine with Core i5 something or other and SSD it takes about 2 seconds for the calculator to appear the first time I push that button. On the Core 2 Duo machine that preceded it, running XP from spinning rust, the calculator would appear instantly - certainly before I can release the button.
But also WinXP was the OS a lot of people used during their formative years - don't underestimate the power of nostalgia.
Also, for some people the very fact that Microsoft don't want you to would be reason enough!
Personally if I were into preserving old Windows versions I'd be putting my effort into Win2k SP4, since it's the last version that doesn't need activating. (I did have to activate a Vista install recently - just a VM used to keep alive some legacy software whose own activation servers are but a distant memory. It's still possible, but you can't do it over the phone any more, and I couldn't find any way to do it without registering a Microsoft account.)
“On the Core 2 Duo machine that preceded it, running XP from spinning rust, the calculator would appear instantly - certainly before I can release the button.”
This reminds me that there’s an NBA rule that disallows any basket made after a clock stoppage with 300ms or less in the clock - i.e. if player A managed to pass to player B who then attempted a shot, it’s impossible for all that to occur before 300 ms has elapsed.
Meaning, I’m sure you remember it fully launched, 100% certainly before the key came back up from your press, but that is impossible.
Your comment reminds me of that rule from baseball that says something about batters and hats, or maybe it was about helmets or something, it doesn't really matter though because the only point of this sports ball rambling is to distract you from noticing that my "nuh uh" has no substance. Did it work?
This is more than a bit out of place on HN in my experience, please, try to engage politely.
I’m not sure what I can say that will qualify as more than “nuh uh” to you, shy of getting a Core 2 Duo running with XP and the same keyboard as OP. That isn’t possible at the moment, is there anything else I could do?
I admit you got me mildly anmoyed with the sports nonsense, sorry about that.
Anyway, you're talking about reaction time, which isn't actually relevant. The time between an action (pressing a button, or flipping a switch) and seeing the result happen isn't the same as the time it takes you to re-act to that something. Flip a light switch, does the light turn off instantly, or does it take a full third of a second? I guarantee you can tell the difference. 300ms of latency is actually huge and easily perceptible, even if it's faster than you can react.
300ms is a lot of time, especially if the calculator.exe was in disk cache already.
300 ms is a long time on a computer, definitely. Just, the autistic side of me has to speak up when it’s wildly unrealistic glorification of the past.
Keypress duration is likely much less than 300 ms, top Google result claims 77 ms on average. And that’s down and up.
I see it being in cache already as sort of game playing, i.e. we can say anything is instant if we throw a cache in front of it. Am I missing something about caching that makes it reasonable? (I’m 37, so only 18 around that time and wouldn’t have had the technical chops to understand it was normal for things to be in disk cache after a cold boot)
If you had used calculator earlier that uptime, it wouldn't be crazy. It's a small exe.
Okay, let's say the cache is cold and you're on an old clunky spinning rust 5400 RPM hard drive. Do the math. How long will it take, worst case, for the platter to spin to where calc.exe is stored?