16 comments

[ 5.8 ms ] story [ 41.0 ms ] thread
> Added back 5ms sleep on Windows 7/8 in (*Process).Wait (reverted f0894a0)

This was interesting!

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?
There's a Windows 9x community too, although maybe not as large.
What applications are base on this? I mean it sounds super charming and nostalgic to drop a line or two which runs on WinXP, but is this actually useful?
Is it hard to write software that compiles and can run on windows XP now? What about like rust and python?
I wonder if some of those things can be solved via a shim DLL that provides the necessary missing WinAPI functions instead of modifying the source code. Although the number of changes required seems vanishingly small anyway, so either approach coukd work just fine.
Strangely, AutoHotKey v1.1 scripts when compiled in ANSI mode runs perfectly on Windows XP.

AHK came in very handy we needed a quick tool to track mill operators, roughly 20-30 lines of code and we had a working GUI app.

Since hardware prices have skyrocketed, it is very important to run software on low-end hardware and use a suitable operating system, such as Windows 7, whose support, amusingly, has been dropped by nearly every project recently. Backporting software to Windows 7 is something we must do, for our freedom and our wallets.
vxkex works really well, give it a try
sadly doesn't work on winxp x86 - just tried. not a valid win32 application.
(comment deleted)