backtop


Print 134 comment(s) - last by kayronjm.. on Apr 17 at 5:26 PM

The truth comes out about User Account Control

Microsoft's Windows Vista operating system has been lambasted ever since it was launched for consumers in January 2007. Diehard Windows users balked at the steep system requirements, sometimes sluggish performance, inadequate driver support, and varying products SKUs at multiple price points.

One feature that has caused quite a bit of controversy with consumers has been the User Account Control (UAC) that is included in Windows Vista. UAC prompts nag users for simple operations such as going to device manager, emptying the recycle bin, or installing/uninstalling an application.

David Cross, a product manager responsible for designing UAC, gave the real reason for UAC at the RSA 2008 conference in San Francisco yesterday. "The reason we put UAC into the platform was to annoy users. I'm serious," remarked Cross.

Cross added that Microsoft's unorthodox method to stop users from wreaking havoc with their systems and to stop software makers from making applications that delved too far into the Windows subsystem was a necessary move.

"We needed to change the ecosystem, and we needed a heavy hammer to do it," Cross added. Cross went on to say that although UAC may be seen as an annoyance to some, but its lasting implications are far more beneficial to Vista users. "Most users, on a daily basis, actually have zero UAC prompts."

Many would say that many users have zero UAC prompts on a daily basis because they have already disabled UAC -- not so says Microsoft. According to Cross, 88% of Vista users have UAC enabled and 66% of Windows sessions do not encounter UAC prompts.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Sluggish Performance
By Funksultan on 4/14/2008 7:45:13 AM , Rating: 4
Well, there is a ripple effect that becomes important here...

The purpose of marking you down is so that you truly understand the difference between int and long, not because it is going to effect the performance of your immediate program, but because it's important for you to know. An easy analogy is ebonics. Yes, we all can understand slang, but if we use ti to the point where we forget the use/spelling of the proper words, we lose something.

In the same way... yes, my quad-core is gonna chew up any code I write for it, pretty much no matter how sloppy I am, so I suppose I don't have to worry about long vs int. I might go years not caring, and eventually forget about ints all together.

What happens when I'm an OS programmer? Or what happens when I've trained 2 generations of junior programmers, and nobody uses ints anymore? Now, instead of a few occurances, the problem starts to magnify.

A coder who knows how things work vs. one who doesn't is like the difference between an architect, and someone nailing boards together. (yes, a Costanza moment)


"When an individual makes a copy of a song for himself, I suppose we can say he stole a song." -- Sony BMG attorney Jennifer Pariser














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki