The problem with UAC is that 90% of users have no idea when it would be necessay to click "no" when that dialog box shows up. For them, it's the box that always annoys you and you have to just click "yes" to make it go away.
I understand what it's supposed to do, but have had it disabled since it was released, and have saved hours of task interruption it in exchange for no other problems.
I strongly disagree with that caveat. As a savvy user, UAC behaves like a burglar alarm for me. I am not savvy enough to open a 7z, PDF, JPG or DOCX in a hex editor and determine whether it contains an exploit. Even if I were alone on the planet due to the ability to do so, I wouldn't have the time to do anything else. Because I have UAC enabled, if I open a zip file and get a UAC prompt I know that something is fishy.
There are known unknowns and your savvy is perfectly suitable for that; however, your savvy won't help at all for the unknown unknowns. Double-clicking an .exe isn't the only way to get pwnd.
> you have to just click "yes" to make it go away.
Exactly, UAC doesn't really work for non-savvy users. In which case, who is the target audience?
MSDN is full of posts and articles how to be a nice guy and run as user, unless of course the application needs to do some low system level calls.
And even then, there are ways to split the architecture between privilege levels.