In retrospective it wasn't the botched hardware design that was the real fiasco for the Xbox 360 since Xbox owners showed that they will put up with defective hardware and continue to fork out hundreds of bucks over and over again for replacement consoles.
And what does that tell you? If you were a third party developer what would that tell you?
A year from now it looks like there will be easily more than a hundred different Sony, third party game, and third party non-game company spaces in Home.
And nobody using any of them.
Actually, a few will be using them. Everyone else with be waiting in the virtual line.
Xbox Fanboys: "Teh 360 is just a powerful as teh PS3"
Hilarious losers.
No one ever says the 360 is just as powerful as the PS3. It's not. What I find interesting is that you'd never know the difference unless you read the specs. The PS3 is a engineering gem and a marketing disaster.
When the PS3 first came out, I derided them for pushing BluRay, which IIRC was the main reason the console came out so late (?). What I've come to realize is that BluRay is the PS3's saving grace. If they had gone with DVDs like the 360 did, there would be little reason to own one.
I own all three consoles, and I find the PS3 to be a capable multimedia machine. I use it to play movies and we've rented some off the PlayStation network. But I only own one game for it, compared to my 4 Wii and 9 360 titles.
No. You can't define "improvement as a concrete metric." That forces schools to fudge numbers and pass students who would otherwise fail. That is a horrible idea. Horrible.
Mark Russinovich, (of sysinternals fame), did a series of videos with David Solomon, and this is one of the topics they covered. So this information comes from them and that video. I suggest everyone check it out some time, those guys probably know more about Windows than most people.
1) No paging file == no crash dumps. Windows writes crash dumps to the paging file on the boot volume. So if you want a full memory dump, you'll need to match your paging file size to your physical memory size.
2) Modified private virtual memory is the only memory that gets written to the paging file. Not code. Code can be read from the same place it got it from in the first place. And only memory that isn't referenced for some amount of time gets paged. So my understanding of that is even though you disable your paging file, CODE can still be "paged out".
3) So, it's slightly more efficient to have a SMALL paging file than none at all. Some memory allocated by software may be used once then never touched again. The paging file gives Windows a place to put it, so the paging file essentially becomes write-only. Then those pages are freed up for the memory manager to use.
4) If you're going to use a paging file, the correct size to use is the sum of the private bytes of user-space programs plus the kernel private bytes. This is known as the "commit charge" which you can see in the lower left hand size of the built-in task manager. That is the "potential page file usage", not the amount of actual paged-out memory.
Personally, I've been running without a paging file for years without issues. Unless I need to do a crash dump analysis.
Get hold of portable property. -- Charles Dickens, "Great Expectations"
