When a large group speak negatively yet wrongly constantly about something, anyone impartial will end up looking biased as they correct those who were incorrect. I also correct those who say something wrong in the other direction, but generally those people are corrected far before I have a chance to say anything.
If you look around this forum, a lot of people here are practically a lynch-mob against NVidia for whatever reason. That's not an opinion either, that's an actual fact. It actually got so bad that I was asked to stay out of the gpu threads entirely for quite awhile merely because correcting people made me LOOK completely biased, even though my information was correct. Same reason most of the staff on this site stay out of GPU threads as I'm sure you'll notice. It was funny to me, because at the time there was a shiny 4850 sitting in my gaming rig, yet people said I was biased against AMD.
Think about that for a second, and things will begin to make more sense to you.
I generally stay out of cpu discussion unless there is something big on the horizon because frankly speaking if you have a c2q or better most of it really isn't a big enough improvement to want to spend your time with. I mean, I'm still on a Q6600, and I haven't seen enough of an improvement over this cpu to warrant buying a new mobo, ram, and cpu yet. Before that Q6600, I only used AMD chips during the P4 vs A64 era, and once the X2's came out I pretty much would NOT touch an intel chip until the C2D showed up.
I go by what works best for what I want to do. If I see a glaring issue(like say, DX9 power on the GeForceFX series) I steer clear of it until it is proven that it's a non-issue. If people aren't informed of that possible issue, I tend to point it out to them. At present, it appears AMD may still not be up to par on tessellation performance. This isn't a sure thing, but it appears to be a possibility, which is why I stated that only time will tell if it's a driver or hardware issue.





Reply With Quote


Bookmarks