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 wetwareinterface on 4/11/2008 3:42:52 PM , Rating: 3
there's an old it joke it goes like this...

2 programmers one from the linux community one from the microsoft campus are at a security convention. the linux guy turns to the microsoft guy and asks what they use in-house to do speed optimization. the microsoft guy responds "speed optimization? it's intel's job to make the code run faster.". and then the microsoft employee asks the linux dev what tools there are on the linux platform to ensure they don't break the tree. the linux dev responds "we use green procesors like transmeta, why?" if you don't know what a code tree is the joke isn't funny, so here it is a code tree is a conglomerate of the different dev teams output and if you introduce something that causes a fault either in your own code or somewhere else it's called breaking the tree.

and this is the problem in software, there are 2 distinct types of coders one type has no development schedule to adhere to and puts what features they want to include ala small independant dev or government or other in-house corporate type it developer. the other type is on a schedule and has a list of features they need to integrate with and add to their own code ala big software house.

one side has the design goal of more efficient code and gets to work against a set system that doesn't change.
the other has the design goal of interoperability and feature compatibility and hiding of features that will break the code module they are working on.

neither side is right or wrong. it's just how it is. making code more efficient isn't the primary goal of an os developer, exposing and hiding features that will make or break the code base is.


"We’re Apple. We don’t wear suits. We don’t even own suits." -- Apple CEO Steve Jobs














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