Ok the word liar was a bit harsh sorry, but i still don't understand how people are *misinformed* when they say that they have tried it on their on machines and their is so much info around on the subject
When I say misinformed, I'm talking about the people who make over generalized statements, like "Vista is a resource hog," or "it's slow."
Vista is not a "resource hog." It does use a lot of resources, but it just doesn't use them and do nothing with them. Most of this complaining is due to "superfetch." Vista is no more of a "resource hog" than Leopard. People on here bash Vista for stuff that they praise Mac OS X for having.
People say that it's slow. In all honesty, I have no idea under what circumstances they're saying it's slow in. Are they talking about in Boot Camp or under virtualization? I'll be the first to admit, Vista would not be an OS I would want to virtualize anytime soon. When XP was released, I wouldn't have wanted to virtualize that on modern hardware from that time. Running two OS's adds a huge burden on an OS, even if it is modern and relatively up to date. If I was going to run Vista in a virtual machine, I would disable some services (such as superfetch and Indexing). I will say that file transfer times still suck for the most part. In some programs, you can see a bit of a performance hit. But it's nothing that I would say is "bad." There's a performance hit in games in XP over 2000 but nobody says anything about that. If you have modern hardware, there shouldn't be any problems.
People claim it's "unstable." Sure it was, after it was released with the crappy Nvidia drivers that were out (and boy, did they SUCK). It's been over a year and half since completion. You shouldn't be seeing problems any more. If you're having driver problems on your Mac, go write Steve Jobs a letter, not Bill Gates. Yesterday I had my first BSOD in Vista, and it was a driver issue. This was on my self-built PC. Vista restarted successfully, and when it said that it may find a solution for the problem, I let it do it (after all, how could it hurt, even though in XP it was useless). To my surprise I actually got a response and it told my nforce SATA drivers caused the crash (which I had a hunch it was a driver problem due to getting the "IRQ_LESS_THAN_EQUAL" error which is usually a driver or memory problem). I installed the latest nforce drivers I could find. Restarted, ran Windows Update, and updated SATA drivers appeared, I installed them and I may have to wait another year and a half for a BSOD.
My Mac had a BSOD once in Vista, because I was using highly unstable alpha software in the beginning stages of development. Not what I would consider a fault with MS or Vista.
Here's something from a thread a few months ago I wrote up:
In a few ways it's similar to Mac OS X's memory usage.
I've had my laptop on for a few days and I'm downloading a Torrent file.
If I was obsessed with having as much free memory as possible, I would absolutely hate Mac OS X.
Currently, I have 10.4 MB of free memory. Free memory is memory that is not being used and that's available. Free memory is actually wasted memory. It's not doing anything. If you buy 10 gigs of RAM and you only use 1 gig of it, the rest of the memory is wasted.
Right now, I have 1.08 GB of Active memory. Active memory is memory that is being used. Similar to opening up the task manager in XP and adding up the memory of each task being used.
I also have 735.98 MB of Inactive memory. Inactive memory is something that's NOT seen in XP. Inactive memory is in Mac OS X is very much like Superfetch in Vista. Inactive memory is memory that is being occupied by program(s) that AREN'T in use. These programs are loaded into memory so that when you want to use them later, they'll load up quicker (RAM is a lot faster than the hard drive). When a program needs that Inactive memory, Mac OS X releases it. This is how Mac OS X can feel so responsive, even when you have something like 10 MB of RAM left. Vista uses memory in the same way. When you open a program and close it, it's cached into the memory. When that memory is needed, Vista releases it. Hopefully this makes sense.
The reason why people are "hating" Vista so much is because this is a new feature that nobody has ever seen before and many people aren't aware of how it works. I've had Vista crash on me a total of 2 times in the 1.5+ years of using it (I used it when it was in RC1, so it's more like 2 years, and RC1 never crashed on me either, but I didn't use it as my main OS due to lack of drivers). 1 time was a driver issue, and the other time was due to me using extremely buggy alpha software. Much of the early hate for Vista was due to immature drivers (the reason why XP didn't suffer from this is because XP used the same driver model that was used since Windows 98). This had since changed. The drivers are pretty much on par with XP's drivers.
This should make a pretty clear comparison between Vista's superfetch and Mac OS X's memory management. The main difference is the lack of a pretty chart in task manager that breaks your memory down for you.
If someone says they don't like Vista, fine. I'm not going to bug them. But when they start spreading FUD, I'll correct them.