easiest thing you'd have to do is write a program that requests an insane amount of RAM despite not intending to actually use any, that's not exactly hard to do. the existence or lack of an example has no bearing on the truth of the statement, its absence merely fails to offer direct evidence for it, that doesn't contradict anything stated at all. I can't think of any examples off the top of my head, because a) I don't disable mine, and b) i try not to run ****ty programs. But you have to be dreaming to assume that every single thing that someone might need is properly written. in fact, is it not the case that the more niche and critical a piece of software is to someone's particular purpose, the more likely it is that it's poorly written? Not everything has readily available alternatives, and the ones that don't are especially likely not to be of high quality. Considering the fact that there's no benefit whatsoever in disabling the page, why would you go take such an unnecessary risk, whether it's likely to manifest or not? the bottom line is that it's pointless even if it's not harmful at all.
The lack of evidence allows me to discard your statement without any evidence.
if you say "Although I have no evidence, Microsoft spies on its users through USB cameras" - there is no need for me to provide evidence for the contrary.
I can simply dismiss this assumption of yours without any evidence.
AFAIK malloc may actually allow a program to do that without allocating that amount of memory. That is it will only actually allocate that memory when it is being written to.
You said "suddenly decides it needs it (not just because there's no memory left" and now you are backing away from that statement.
"insane amount of RAM" is not explicitly manipulating the page file.
For a program swap and RAM are nothing more than a singular large pool of memory to use. I advocate only have the fast (RAM) memory without the slow (PF) memory for everyone who has a good or insane amount of memory.
When it comes down to it you are advocating running Windows in, essentially, "compatibility mode" to allow it to trash your HDD when a rouge and/or idiot made 64-bit application goes haywire instead of keeping the application entirely in memory
and killing it off sooner (before the Windows will start allocating more and more HDD space for the rouge application).
Thus, as an SSD and 32GB RAM user, I cannot agree with the statement that "there's no benefit whatsoever in disabling the page".