Slow and clunky - a by product of using .NET for something that patently doesn't suit the job (particularly in terms of an app that runs at startup!). Sometime it takes two launches to start CCC at all, and on both my work and home pc's it's _so slow_ that i can see individual UI elements being drawn. It's just not right for the job and I wouldn't make the same mistake in my own software (which also has startup components) as our customers would complain (as ATI users do quite vocally on the subject).Originally Posted by Smokey21
The drivers themselves have nothing to choose between them (at least in my experience) on Windows. It's the peripheral software in ATI's case that let's them down - and whilst I know .NET is 'the future' it wasn't the right time to choose it - who on earth wants to twiddle their thumbs waiting for .NET to load it's 8 billion DLLs just to show a simple control panel? Bottom line is (for me) I couldn't care less which company produces the best solution for me - and so I switch 'sides' (god knows why there's even that concept - neither corporation 'cares' about you) regularly. ATI (IMHO) have a better solution right now with HDR+AA than nVidia, and so that's where I am. If the next gen part from nVidia is better i'll go there. Driver's are secondary issue as i've never really had that much of a problem with either (aside from the very early days with a Rage 128!) but boy, CCC don't half wind me up. Perhaps it's because i'm a developer and I can't help but think 'i could of done a better job with good old ropey MFC'.Originally Posted by Steve
I may be wrong but on Vista I think both companies will be forced to comply with MS' new control panel style and perhaps it will resolve the issue for both sides.