kyube wrote: ↑15 Oct 2025, 11:36
You should read these forums more often to understand why my manner is variable depending on the type of post in question.
I also fail to understand why you've necro'd such a old post in the first place, but let's move past that...
The user you're trying to defend (let's assume you're not one of the 50 different alt accounts which "spams" nonsense here) has shown clear lack of interest in approaching this topic in a matter of how Windows performance troubleshooting is supposed to be handled.
If someone doesn't want to read the official, recommended and "bulletproof" way on how to figure out performance problems on Windows & then continues rambling
clear nonsense without any sources or proof, what else is left other than point out the errors?
These things being discussed here aren't intangible, nor something abstract.
They're practical, concrete & specific software "problems" which can be "fixed" using methods described by 1st party sources (Microsoft Nvidia, AMD,...), most of which are written by
HW/SW engineers
"Feelings" are prone to human (physiological, psychological, environmental) bias, therefore cannot be used as extrapolation onto every possible hardware & software combination.
Either way, majority of these "problems" purported around here have been solved ages ago or lack incentive to be tested properly due to lack of knowledge & lack of dedication.
Trolling seemingly sells better.
Have fun with whatever you're trying to do.