Plus, if something seemingly can’t be terminated with that, 99% of the time it’s a kernel level lockup (e.g. disk IO). At which point you only have 2 options: kill it via a kernel debugger or (the more likely scenario) perform a reboot.

Precisely. MS didn’t do a very good job maintaining it for Ryzen CPUs recently, though. I remember the whole fiasco with Zen 4, when it just came out, it ran better on Windows 10 than 11.

Then, more recently, 9950X3D needs manual thread pinning to run some games better.

Like, come on… this isn’t something any user should even be worried about.

But also keep in mind that “just talking to the hardware” is one hell of a reduction and oversimplification, too.

Keep in mind, these issues with Ryzen scheduling are fairly new. People yap about NT being an issue when it wasn’t for many years and it still isn’t even the primary issue (and it usually gets fixed by the vendors themselves in one way or another).

In fairness to Windows, the kernel and the drivers are the few of the objectively good things about it.

Neither NT nor its age are the problem. It should be a testament to how well it works for the things we’re using it for today.

The problem is the userspace. The things that you interact with and see. That is what you’re referring to when you mention “the format dialog”. Not NT. Win32 isn’t a kernel, it’s an API that is used to sometimes talk to NT indirectly and give userspace functionality.

Where NT is truly starting to show its age is with things like scheduling on AMD Ryzen chips with 2 different CCDs. That is a Microsoft skill issue. Had this issue cropped up not even 10 years ago, they would’ve figured it out. This is what is gonna age NT. New hardware, not new software.

From a glance, this is just a value parser that exports them by symbols and allows you to edit the static values from a file neatly.

I don’t know how practical this is yet since I haven’t seen the video, but in order for it to be more practical it needs to be easier to implement and use than other methods to accomplish tweakable values for debugging.

There are many already:

• parsing a config/text file in runtime
• parsing commandline args
• parsing environment variables
• using a debugger and a memory watch
• using external tools that can edit memory

Now, not all methods are available on all platforms, but, it needs to be better than any of these methods in some way for it to have any point in using it.

Game devs often have their own frameworks that can communicate with the game via network to tweak exposed values anyway for realtime debugging. Adjust.h from what I can see requires the program to be reset on each iteration.

Oh you mean Android Studio automagically “updating” your versions so that your build breaks and you spent 3 hours figuring out what just happened without you even touching anything?