New
#31
That may be one of it's uses,, but lets say a programmer ignores that advice and turns off UAC to code? Then what?It's a hindrance that MS created to teach Win32 programmers to program the correct way (that is to honor non admin user class, and not call anything that is system critical directly).
1 ,, you answer the simple question in your own post several times, trying to discount the need for UAC, quite simply, contradictions abound.Here's the thing, UAC is created so that we all can use our "Admin" class users without being an actual Administrator, that's it.
2 ,, no explanation needed.It virtualize every app we call into UAC sandbox automatically. Unless specifically asked, no app will run with Admin privilege EVEN IF you are an Admin.
3 ,, However, Linux and Unix will not let a stupid programmers code run that requires root access without typing in the root user password. Unless you are running as root. Duh!UAC is one of MS's "stupid" solution to a classic multi user system problem that have been solved many years ago in Linux/UNIX.
Actually, it's good to know when any program is requesting admin rights to run.If you use a limited user account for day to day use, UAC is adding useless processing overhead, it's useless in a limited user case because the user it self is already limited.
I sure as hell want to know what is requesting admin access to run on my system regardless. I personally thinks it is really really stupid to NOT want to know what an app is requesting admin rights to run.
4 ,, Yes,, stupid,, I think we should all go the root user way and require a password be typed in. Yee haw, can you see the shear number of posts for that?UAC is made to limit an admin account so that it loses it's "admin" privilege unless the users agrees the UAC confirmation box that a program requests "Admin" privilege, which is stupid at best.
And for you that's fine, it's not good advice though no matter how you try to spin it.I can't really deny the fact that there are more novice users in Windows world, MS caters them... It's not MS's fault... I still disable UAC, I don't see the point of it's active in my system. I use limited user for day to day use, and fast user switch to admin to install things. Everything runs faster without UAC (do not ask the speed difference because I have 110++ processes upon boot up, my rig is running as a development workstation and a DB server and a virtualization server, all in one). But this is me and my computer, and my close friends, and my colleagues...
zzz2496
I don't really mean any disrespect through this post, but come on, seriously?